You can ignore that half finished sentence I meant to remove once I decided to ask for mroe info :)
On 6 August 2013 17:57, Robbie Gemmell <[email protected]> wrote: > Hi James, > > Can you elaborate on the full state of the cluster (e.g both nodes > running, second node only running because first node went down while it was > the master, what the desginatedPrimry settings were etc) and also how it > got into that state (e.g killed the first node while it was master, pulled > the netowrk cable, etc etc). The behaviour can be fairly subtle at times > and the below doesn't really provide enough information to fully reason > about. > > Robbie > > When you said below that you tried 'un designating' the > > On 6 August 2013 17:43, jbelch <[email protected]> wrote: > >> Keith, >> >> I can successfully set the DesignatedPrimary attribute to true on the >> passive node and nothing changes. It still thinks the original master is >> the master. The NodeState attribute never changes when I toggle the >> DesignatedPrimary back and forth. I also attempted to set the >> DesignatedPrimary attribute to false on the active node and I don't see a >> change, either. What am I missing? The NodeState does not change. I >> attempt to "removeNodeFromGroup" from my Jconsole and it even disallows >> removing the original master because it still thinks it's the master node. >> Any thoughts? >> >> James >> >> >> >> -- >> View this message in context: >> http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Master-Failure-and-Recovery-tp7596360p7596548.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] >> >> >
