[rabbitmq-discuss] Confirm consistent hash exchange behavior

Matthias Radestock matthias at rabbitmq.com
Fri Mar 15 22:57:19 GMT 2013

On 15/03/13 22:49, Brett Cameron wrote:
> Could you possibly get around this by extending Alvaro's idea a little
> bit, and have consumers do a basic.reject with requeue=true on messages
> (queue names) consumed from the "lock" queue?

The whole point of the "lock" queue is to ensure that at most one 
consumer consumes from a given queue. Requeueing messages there, and 
thus releasing the lock, would break that.


More information about the rabbitmq-discuss mailing list