No subject

Thu Mar 14 15:04:54 GMT 2013

The minute you join one node to another to form a cluster something<br>
dramatically changes: not every node has a full copy of every queue.<br>
In a single node setup all of the information about a queue (metadata,<br>
state, and contents) is fully stored in that node (Figure 5.1).<br>
However, in a cluster when you create queues, the cluster only creates<br>
the full information about the queue (metadata, state, contents) on a<br>
single node in the cluster rather than on all of them (the cluster<br>
tries to evenly distribute queue creation amongst the nodes). The<br>
result is that only the =93owner=94 node for a queue knows the full<br>
information about that queue. All of the =93non-owner=94 nodes only know<br=
the queue=92s metadata and a pointer to the node where the queue<br>
actually lives. So when a cluster node dies that node=92s queues and<br>
associated bindings disappear. Consumers attached to those queues lose<br>
their subscriptions, and any new messages that would have matched that<br>
queue=92s bindings become blackholed.<br>
Does this mean, when a client create a queue in the cluster, this<br>
queue is created on a random(?) node of the cluster, not the connected<br>
node =A0for the client?<br>
rabbitmq-discuss mailing list<br>
<a href=3D"mailto:rabbitmq-discuss at">rabbitmq-discuss at lis=</a><br>
<a href=3D"
cuss" target=3D"_blank">


More information about the rabbitmq-discuss mailing list