On 04/30/2013 06:09 AM, Christian Fromme wrote:
Hi list,
On Sun, Apr 28, 2013 at 6:42 PM, Salman A Baset <[email protected]> wrote:
The master starts ok with /etc/init.d/qpid-primary. The master becomes
active.
I start the slave using service qpidd restart. Slave starts in ready state.
I then restart slave. It remains in catchup state. This is very weird
behavior. Even after multiple restarts of slave, it remains in catchup
state.
Maybe we have a similar problem with Active/Passive clustering
(version 0.20). When I restart the primary, the slave stays in state
"ready" and former primary stays in state "joining":
$ ./qpid-ha -b 10.40.48.1 status # Former primary, restarted
joining
$ ./qpid-ha -b 10.40.48.2 status # Former slave, staying in ready state
ready
Is this expected? I would expect the former slave to become "active"
by itself. Maybe I'm mistaken.
Sorry, my previous answer was too hasty. Qpid requires an external agent to
detect failure of the primary and pick one of the backups to take over.
Currently you can use cman and rgmanager (from cluster suite) to do this as
explained in the documentation. If you have another cluster resource manager it
would be fairly easy to use it instead. The link between rgmanager and qpid is
just the qpidd-primary script, another manager might also be able to use this
directly, or a similar script could be written.
Cheers,
Alan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
