classic mirrored queue，producer and consumer connect to different node，has diff tps。 #9016
-
Describe the bugclassic mirrored queue， producer connect master node， consumer connect mirror node，the tps is 3500 message， but produc and consumer both connect to masternode， the tps is 17000， how is that ？ Reproduction stepsclassic mirrored queue， producer connect master node， consumer connect mirror node，the tps is 3500 message， but produc and consumer both connect to masternode， the tps is 17000， how is that ？ Expected behaviorthe tps is almost same。。。。 Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Classic mirrored queues is a feature that has been deprecated and will be removed from RabbitMQ in early 2024. It's a data locality effect. Consumers do not consume from mirrors (followers) in the case of classic mirrored queues. This is a yet another reason to migrate to quorum queues where consumers can get deliveries directly from followers (but acknowledgements still flow through the leader). |
Beta Was this translation helpful? Give feedback.
-
|
Data locality matters for all the messaging protocols RabbitMQ supports, for all queue types but specifically for the long deprecated classic mirrored queues where all operations, including deliveries, goes via the node that hosts the leader replica. This is not really the case for streams because clients discover the topology and connect to the nodes where the replicas are. This has its own downsides but as far as throughput goes, is a helpful protocol design decision. |
Beta Was this translation helpful? Give feedback.
Classic mirrored queues is a feature that has been deprecated and will be removed from RabbitMQ in early 2024.
It's a data locality effect. Consumers do not consume from mirrors (followers) in the case of classic mirrored queues.
This is a yet another reason to migrate to quorum queues where consumers can get deliveries directly from followers (but acknowledgements still flow through the leader).