[rabbitmq-discuss] Clustering Issue

Jorge Varona jvarona at attinteractive.com
Fri Aug 28 22:22:07 BST 2009

I've noticed some issues with clustered boxes that are weird. For
example, in a two-box cluster I have Client A sending messages to Server
A and Client B pulling messages from Server B. We already know that if
we shut down Server A (it was first to declare a queue) messages stop
being delivered to Server B and in turn Client B. The strange behavior
I've noticed is that if I bring Server A back up and send messages to it
they are not relayed to Server B, which has Client B attached. Only
after I restart Server B do messages begin to be relayed to Client B.


Here are my assumptions:

1. Queues exist only on the server on which they were first declared.

2. Nodes within a cluster relay requests to the server on which the
queue exists instead of messages being relayed to the server after first

3. If one node is down (I only tested the one on which the queue was
created) all nodes must be restarted to re-commence replication-like
behavior in the cluster.



Has anyone experienced the same behavior? Could this be due to bad
configuration? If not, are there efforts to address these
issues/scenarios? Thanks.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090828/70ec83a2/attachment.htm 

More information about the rabbitmq-discuss mailing list