You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2017/03/13 13:39:41 UTC

[jira] [Created] (AMQ-6625) IOException in kahaDB needs to pause pending IOExceptionHandler intervention

Gary Tully created AMQ-6625:
-------------------------------

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