qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbelch <jamesbe...@verizon.net>
Subject Qpid Java Broker - Master Failure and Recovery
Date Thu, 01 Aug 2013 21:51:43 GMT
In your High Availability documentation for the Java Broker, section "
- Depictions of cluster operation" has a section called "Master Failure and
Recovery" which describes the sequence of events for a master failover and
the replica taking over the master's role.  One of the items states the

3.  A third-party (an operator, a script or a combination of the two)
verifies that the master has truely failed and is no longer running. If it
has truely failed, the decision is made to designate the replica as primary,
allowing it to assume the role of master despite the other node being down.
This primary designation is performed using JMX.

I am able to get the BDBHAMessageStore bean and set the "DesignatedPrimary"
attribute to true for the replica server in the case the master fails.  What
else do I need to do for the replica to take over as master.  Do I need to
set anything else?  Do I need to cycle the replica or will it take over the
master role simply by setting attributes to tell it that it is assuming the
master role?


View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Master-Failure-and-Recovery-tp7596360.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message