[
https://issues.apache.org/jira/browse/AMQ-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296454#comment-14296454
]
Anuj Khandelwal edited comment on AMQ-5540 at 1/29/15 6:41 AM:
---------------------------------------------------------------
I have updated the request with more details. Please check once.
was (Author: anujkhandelwal):
I have updated the details. Can you check now ?
> 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
> Attachments: ActiveMQ_config.xml, Logs.txt
>
>
> 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
> .
> Scenario : We had some failure on filer because of which applications
> (ActiveMQ) was not able to read/write on kahadb. I have attached the logs to
> see the details. Master broker was not completely killed. Master has stopped
> it's transport connectors and plugins but it didn't release it's lock from
> the kahadb. I have checked from "ps" command that master broker was running.
> And since master didn't release the lock on kahadb, slave broker was not able
> to acquire the lock.
> Master broker should shutdown properly in such cases and let the slave take
> over the persistence store.
> Thanks,
> Anuj
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
