[rabbitmq-discuss] Distribution model advice sought

[Mark J. Reed]

On Thu, Mar 3, 2011 at 2:24 AM, Matthias Radestock
<matthias at rabbitmq.com> wrote:
>> Our initial design had a single exchange with N queues bound to it;
>> each of the M consumers then subscribes to one of the N queues.
>> Simple.
>
> How do you avoid the producer having to publish the message N times in this
> setting? I am asking because there is a new feature appearing in the next
> release that addresses that very problem :)

Fanout exchange.

> When a node goes down, taking all its queues with it, the clients connected
> to that node and consuming from the queues will have their connections torn
> down. They would notice that and could simply reconnect and redeclare the
> queues & bindings & their consumers.

The problem I'm seeing is that the surviving nodes seem to remember that
the queue was declared on the dead node and fail when attempting to
declare it again.