I thought the master was killed completely, and the problem was solely that the slave didn't take over. Can you please describe how the master wasn't killed completely, since you've never before mentioned that in either your emails here or the JIRA you submitted?
On Tue, Jan 27, 2015 at 7:46 AM, khandelwalanuj <khandelwal.anu...@gmail.com > wrote: > Hi, > > There was some failures on filer because of which applications (ActiveMQ) > was not able to read/write on kahadb. > > As you mentioned that kahadb should handle this if master broker is not > writing than failover should take over; I have logged a request > https://issues.apache.org/jira/browse/AMQ-5540 > > To handle this can ActiveMQ provide a configuration in > http://activemq.apache.org/configurable-ioexception-handling.html which > can > kill the master completely and let the failover take over ? > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException-Input-output-error-tp4690378p4690470.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
