Submit this as a JIRA, stating that KahaDB can't fail over to the slave if the master is unable to write to disk when it shuts down (because it couldn't write to disk). I'm not sure how feasible it'll be for the slave to detect this (maybe there's a file modification timestamp that can be used, or maybe something could be added to have the master write periodically to a file so the slave can detect that the master is no longer writing), but ideally KahaDB should handle this situation.
With that being said, have your sysadmins figured out why KahaDB was unable to write to disk in a live production system and made sure it never happens again? Because KahaDB only had this problem because your infrastructure had a terrible failure, and I really hope that the sysadmin's office, not the ActiveMQ mailing list, was the first stop you made after you discovered this problem. On Jan 26, 2015 11:24 PM, "khandelwalanuj" <khandelwal.anu...@gmail.com> wrote: > Did anyone get a chance to look at this ? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/kahadb-corruption-Checkpoint-failed-java-io-IOException-Input-output-error-tp4690378p4690442.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
