Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6625

IOException in kahaDB needs to pause pending IOExceptionHandler intervention

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.14.0
    • Fix Version/s: 5.15.0
    • Component/s: KahaDB
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gtully Gary Tully
                Reporter:
                gtully Gary Tully
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: