You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read this issue #262 which is open since 5 years. Does it mean there are no plans adding this feature at all? If yes, what are the reasons that it won't/can't be added?
In my opinion this is one of most useful features, both Kafka and ActiveMQ support this. It allows processing messages in order with some degree of concurrency. For now the only way to preserve message order is to either use single active consumer with prefetch_count = 1, which allows only one message processing at the same time (even if some of the messages could be processed in parallel) or use rabbitmq_consistent_hash_exchange which complicates topology a lot I think.
You don’t have to use prefetch of 1 for single active consumer ordering.
Any prefetch is fine and it will retain the input order. SAC with
consistent hash exchange is a good but underused pattern to follow IMO.
On Sun, 5 Jun 2022 at 11:13, Aleksander Barszczewski < ***@***.***> wrote:
I read this issue #262
<#262> which is open
since 5 years. Does it mean there are no plans adding this feature at all?
If yes, what are the reasons that it won't/can't be added?
In my opinion this is one of most useful features, both Kafka and ActiveMQ
support this. It allows processing messages in order with some degree of
concurrency. For now the only way to preserve message order is to either
use single active consumer with prefetch_count = 1, which allows only one
message processing at the same time (even if some of the messages could be
processed in parallel) or use rabbitmq_consistent_hash_exchange
<https://github.com/rabbitmq/rabbitmq-server/tree/master/deps/rabbitmq_consistent_hash_exchange>
which complicates topology a lot I think.
Here is how it works in ActiveMQ:
https://activemq.apache.org/message-groups
If there is RoundRobin message distribution between consumers in RabbitMQ
then is it complicated to add hash-based distribution?
—
Reply to this email directly, view it on GitHub
<#4974>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJAHFCTAAOOHENHEBAK3X3VNR4VBANCNFSM5X42TPZA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
I read this issue #262 which is open since 5 years. Does it mean there are no plans adding this feature at all? If yes, what are the reasons that it won't/can't be added?
In my opinion this is one of most useful features, both Kafka and ActiveMQ support this. It allows processing messages in order with some degree of concurrency. For now the only way to preserve message order is to either use single active consumer with prefetch_count = 1, which allows only one message processing at the same time (even if some of the messages could be processed in parallel) or use rabbitmq_consistent_hash_exchange which complicates topology a lot I think.
Here is how it works in ActiveMQ: https://activemq.apache.org/message-groups
If there is RoundRobin message distribution between consumers in RabbitMQ then is it complicated to add hash-based distribution?
The text was updated successfully, but these errors were encountered: