[rabbitmq-discuss] Confirm consistent hash exchange behavior
brett.r.cameron at gmail.com
Fri Mar 15 22:49:45 GMT 2013
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?
On Sat, Mar 16, 2013 at 11:37 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:
> On 15/03/13 21:56, Alvaro Videla wrote:
>> - Create queues 1, 2, .... N
>> - Bind queues to the CHX
>> - publish the queue names to a queue called "lock" for example.
> With that approach the number of consumers must be exactly the same as the
> number of queues; if you have fewer then some messages won't get consumed,
> and if you have more then some consumers won't process any messages.
> Furthermore, you cannot add/remove queues since that will cause some
> subsequent messages to get routed to different queues than prior to the
> queue addition/removal. They will then be picked up by different consumers.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss