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 Wed, 28 Jan 2015 06:35:35 GMT

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

Anuj Khandelwal updated AMQ-5540:
---------------------------------
    Attachment: ActiveMQ_config.xml
                Logs.txt

Attaching the logs and ActiveMQ configuration file.

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

Mime
View raw message