[rabbitmq-discuss] Repairing a crashed cluster - Obtaining persisted msgs from master

ranjitiyer ranjitiyer at gmail.com
Wed May 1 17:11:48 BST 2013

Hi Simon,

> Note that since that message, RabbitMQ 3.0 was released, with 
> "rabbitmqctl forget_cluster_node" - which might help you get the slave 
> started if the master is gone. 

But isn't this option available only after the rabbitmq server has started
(erl.exe) and I've noticed even erl.exe won't start on a slave machine if
its remote master is not available?

>But what are you trying to do? If the master is still available and more 
>up to date than the slave then why are you removing it? 

Perhaps my understanding is incomplete. When a newly added slave is yet to
be synchronized (http://www.rabbitmq.com/ha.html#unsynchronised-slaves) and
the master (with messages yet to be mirrored across to the slave) dies, does
the hitherto unsynchronized slave, become a fully synchronized master?

My concern was that if this didn't happen, then the newly appointed master
wouldn't have some messages because it wasn't fully synchronized and there
would need to be a way to pull those from the old master DB. (can assume
there is access to the master's db file).


View this message in context: http://rabbitmq.1065348.n5.nabble.com/Repairing-a-crashed-cluster-Obtaining-persisted-msgs-from-master-tp26310p26334.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list