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.
Slave should definitely become active by itself. What version of Qpid are you
using? Would it be possible
to try your scenario with the latest release candidiate at
http://people.apache.org/~jross/qpid-0.22-rc2/ ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
