Uploaded image for project: 'Bookkeeper'
  1. Bookkeeper
  2. BOOKKEEPER-126

EntryLogger doesn't detect when one of it's logfiles is corrupt

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Duplicate
    • None
    • None
    • None
    • None

    Description

      If an entry log is corrupt, the bookie will ignore any entries past the corruption. Quorum writes stops this being a problem at the moment, but we should detect corruptions like this and rereplicate if necessary.

      Attachments

        Issue Links

          depends upon

          Sub-task - The sub-task of the issue BOOKKEEPER-293 Periodic checking of ledger replication status

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. BOOKKEEPER-199 Provide bookie readonly mode, when journal/ledgers flushing has failed with IOE

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. BOOKKEEPER-199 Provide bookie readonly mode, when journal/ledgers flushing has failed with IOE

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              ikelly Ivan Kelly
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: