You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2015/01/27 23:34:34 UTC

[jira] [Comment Edited] (AMQ-5540) KahaDB can't fail over to the slave if the master is unable to write to disk

    [ https://issues.apache.org/jira/browse/AMQ-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294318#comment-14294318 ] 

Gary Tully edited comment on AMQ-5540 at 1/27/15 10:34 PM:
-----------------------------------------------------------

please attach some logs or stack traces so that is is possible to ascertain the state of the master. And attach your xml config.


was (Author: gtully):
please attach some logs or stack traces so that is is possible to ascertain the state of the master. And attach your xml config.

> KahaDB can't fail over to the slave if the master is unable to write to disk
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-5540
>                 URL: https://issues.apache.org/jira/browse/AMQ-5540
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Message Store
>    Affects Versions: 5.10.0
>         Environment: Using Master-slave topology with shared kahadb. 
> Using KahaDB on NFS. 
>            Reporter: Anuj Khandelwal
>
> This is coming from http://activemq.2283324.n4.nabble.com/kahadb-corruption-quot-Checkpoint-failed-java-io-IOException-Input-output-error-quot-td4690378.html#a4690442 . 
> 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). KahaDB should be able to detect such failures and allow slave broker to acquire the lock.
> Thanks,
> Anuj



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)