Hi, I am playing with Master/Slave recently, it seems when Slave starts up, it will talk to a Master and the Master starts to send msg/cmd etc. to the Slave, but when the Slave is down, the Master only deregister the slave, write an error message like "ERROR MasterBroker - Slave Failed" and continue going. When Slave comes up again, it can still successfully register with Master, and start to backup msgs from the Master again, and it will replace the Master when the Master is down, but they are already out of sync.
This make the admin work really hard. Any suggestions? Thanks Erin -- View this message in context: http://www.nabble.com/Master-Slave-in-4.0-t1596345.html#a4331007 Sent from the ActiveMQ - Dev forum at Nabble.com.
