-
1. Re: Any way to configure duration time to delay backup activation
gaohoward Nov 18, 2012 9:30 PM (in response to dengyong)Why dont you let the backup to take over automatically before you start up the live again? In real case I believe if your live crashes, it would take some time to investigate by you anyway. If your script just simply restarts it immediately, it could mostly result in a failure again and again.
-
2. Re: Any way to configure duration time to delay backup activation
dengyong Nov 19, 2012 2:26 AM (in response to gaohoward)Gao:
HornetQ master may crash for different reason like JVM issue. A restart may make the master work. So if the watch dog can restart the hornetq successfully, I don't want backup to take over during the duration. Otherwise, there will be two time live nodes switch. First time, live node switches from master to backup. Second time, after master recovers, live node will swtiches from backup to master.
In fact, I also think this is not hard to enhance. Here is the rough idea:
In org.hornetq.core.server.impl.FileLockNodeManager.awaitLiveNode() codes, when backup nodes get the live lock and the lock status is alive, it will wait a duration. If it still can get the live lock after the duration, the API will return and backup will activate
What do you think of the idea?
Yong Hao Gao wrote:
Why dont you let the backup to take over automatically before you start up the live again? In real case I believe if your live crashes, it would take some time to investigate by you anyway. If your script just simply restarts it immediately, it could mostly result in a failure again and again.