Hi Alan, The issue seems to have been resolved in 0.22. It is present in 0.20.
Thanks Salman From: Alan Conway <[email protected]> To: [email protected], Date: 04/29/2013 09:16 AM Subject: Re: A second restart of slave leaves it in catchup state Hi Salman, Thanks for reporting this. Could you please test with the 0.22 release candidate to see if the issue has already been fixed? You can get it from: http://people.apache.org/~jross/qpid-0.22-rc2/ If you still see a problem let me know and I will get it fixed. Cheers, Alan. On 04/28/2013 12:42 PM, Salman A Baset wrote: > > > Hello, > > I am facing an issue with slave restart and am wondering if others have > also experienced it. I am running 0.18 version of Qpid in active-passive > HA. > > 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. > > Here is qpidd.conf on active and passive nodes. > > # qpid.conf > cluster-mechanism=DIGEST-MD5 ANONYMOUS > auth=no > > ha-cluster=yes > ha-brokers-url=172.16.1.27,172.16.1.28 #(27 is active IP address, 28 is > slave) > ha-public-url=172.16.1.27,172.16.1.28 > ha-replicate=all > ha-backup-timeout=5 > > log-level=yes > log-enable=debug+ > log-to-file=/tmp/qpidd.log > > > Thanks > Salman > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
