[rabbitmq-discuss] Cluster nodes stop/start order can lead to failures

[jbdupont]

Ok, I understand the reasoning behind this behaviour.
However, how can I unlock the situation of the node that I cannot restart at
the moment?

My app is such that node2 is the normal, node1 is used as backup is node2
fails.
When I restart I may be in a situation where node2 is started first and then
node1 - at present I fall into a lock situation.

Is there a way to start afresh node2 without being stuck in the current
situation?
For instance restarting out of the cluster, and then joining the cluster
again ?

That would suit my needs actually.

Othewise, I would need to design a different architecture without cluster...
This may be the way I will have to go.

Thanks to point me into the right direction on this.
Regards,
jb



--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Cluster-nodes-stop-start-order-can-lead-to-failures-tp21965p24586.html
Sent from the RabbitMQ mailing list archive at Nabble.com.