[rabbitmq-discuss] RabbitMQ Consistent Hashing Exchange

John Turner john.turner at thoughtforge.net
Wed Jul 3 11:57:39 BST 2013

Hi All,

I'm very familiar with JMS and have used the GroupID extension to provide 
processing affinity to a single consumer.  For further information on how 
this works see this ActiveMQ 
documentation: http://activemq.apache.org/message-groups.html

This solves the following requirement:

* Messages are distributed to a queue with a GroupID header.
* The broker guarantees that messages with a specific GroupID (say '1234') 
will only be processed by a single consumer.
* If the consumer fails (i.e. the connection is broken or closed), the 
broker will allow another consumer to process messages with that GroupID

Using RabbitMQ and the Consistent Hashing Plugin does not not appear to 
solve the problem because if we are using static (durable) queues, the 
consumer failover mechanism needs to be implemented outside the server. 
 Does anyone have any insight into this problem they could share?

An alternative would be to extend the queue to ensure apply the same 
consistent hashing mechanism to the actual queue rather than the broker. 
 Does anyone know if it si possible to extend the queue implementation? 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130703/6cbfc61c/attachment.htm>

More information about the rabbitmq-discuss mailing list