activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anuj Khandelwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5540) KahaDB can't fail over to the slave if the master is unable to write to disk
Date Thu, 29 Jan 2015 06:39:34 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anuj Khandelwal updated AMQ-5540:
---------------------------------
    Description: 
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






  was:
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







> 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)

Mime
View raw message