The host:port information in the XML configuration is only used when first joining or creating the cluster. After that, BDB stores the cluster information itself in the store files and references that.
You should only need to update the configuration if you blow away the store files for the node that originally created the cluster (by virtue of having itself as helper in the XML) and then wanted to bring it back up and have it rejoin the existing cluster by restoring from the other node (since you would now instead need to set that node as the helper). Robbie On 6 August 2013 20:43, jbelch <[email protected]> wrote: > Thanks for the detailed response. In the case where my master node fails, > I > can set the DesignatedPrimary flag to true in the Replica node. I see the > NodeState transition to "MASTER". In the original configuration, the > replica node was pointing to the master host's 5001 port for the > HelperHostPort. If that machine is no longer there, do we need to update > the new "MASTER"? The new "MASTER" still has it's helper port set to the > original master node, which may not be available, and it doesn't look like > it updates to a local port. > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Master-Failure-and-Recovery-tp7596360p7596575.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
