[
https://issues.apache.org/jira/browse/AMQ-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907488#comment-15907488
]
ASF subversion and git services commented on AMQ-6625:
------------------------------------------------------
Commit c5a8b2c8b11121f4999d9f05932cd040d8c9f2a7 in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c5a8b2c ]
[AMQ-6625] ensure kahadb stops operation on the first IOException to facilitate
auto recovery from partial writes
> IOException in kahaDB needs to pause pending IOExceptionHandler intervention
> ----------------------------------------------------------------------------
>
> Key: AMQ-6625
> URL: https://issues.apache.org/jira/browse/AMQ-6625
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
> Affects Versions: 5.14.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> KahaDB can recover from kill -9 by replaying the journal from the last
> checkpoint or by detecting and reapplying partial writes to the index.
> However this activity is compromised if the journal or index accepts
> subsequent writes. It an lead to skipped write batches or skipped partial
> updates to the index.
> The desirable behaviour of treating an IOException as fatal and stopping the
> broker in the knowledge that it will restart and fully recover needs to treat
> the first IO error as fatal and by default not accept any further writes.
> A more advanced IOException handler can facilitate staying alive in more
> specific scenarios and reactivate kahadb.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
