Re: Failover very slow with kahadb while restart of master is fast

[artnaseef <ar...@artnaseef.com>]

Does the shutdown of the broker complete cleanly in both cases?

A slow shutdown will lead to the shutdown script using kill -9, which
eliminates any possibility of the process continuing to ensure a clean
shutdown.  In that case, the contents of the file may be left in a dirty
state, which may lead to recovery when the broker starts up.

Also, in the "Stop master then stop second master" scenario, is the second
master (B) completely stopped before restarting the first master (A)?

One way to help track this down - take periodic stack dumps (jstack is good
for this) during the startup (perhaps one every 15 seconds), and look at the
stack trace of the main broker startup thread.  That should help determine
the cause.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Failover-very-slow-with-kahadb-while-restart-of-master-is-fast-tp4707500p4708777.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.