Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6520

Improve tail compactions resilience when base state cannot be determined

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.7.6, 1.8.0
    • segment-tar

    Description

      This is a follow up to OAK-3349: in tail compaction the FileStore.GarbageCollector.getBase() might fail to determine the base state to rebase onto. In this case we should fall back to full compaction and report (log, JMX) the problem and its exact cause.

      Failing to determine the base state might be caused by a missing or invalid gc.log file or a invalid or missing record id for the base state being recorded in gc.log. None of these cases should impact system stability.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mduerig Michael Dürig
            mduerig Michael Dürig
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment