[rabbitmq-discuss] rabbitmq clustering using mirrored queues

Venkat vveludan at gmail.com
Sun Nov 20 22:49:30 GMT 2011

Good evening.
We are testing out mirrored queues using RabbitMQ 2.6.1 and spring-
amqp 1.0 on Cent OS in cloud environment.
Assuming that we create a cluster with the following criteria:
- Create cluster with two RabbitMQ nodes Node1 and Node2 (Node2 is
clustered with Node1).
- Queues are created with x-ha-policy = all

Once the cluster is set up and everything is up and running, Node1 is
down (hard failure for the purpose of testing). In cloud environment I
may not be able to bring back Node1 instead a brand new Node is joined
to the cluster. In other words the Master node Node1 is not there
anymore. Could you please let me know what could be consequences in
this situation.

Referring to http://www.rabbitmq.com/ha.html:
All actions other than publishes go only to the master, and the master
then broadcasts the effect of the actions to the slaves. Thus clients
consuming from a mirrored queue are in fact consuming from the master.

I am concerned about the above said, would there be any damage done to
the slave node Node2 in case Node1 (master) is not retained and a
brand new node is joined to the cluster. Could you please suggest
better approach in a situation where a Master Node cannot be brought
back at all.


More information about the rabbitmq-discuss mailing list