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

Estimation for FULL can be off sometimes

    XMLWordPrintableJSON

    Details

      Description

      Since OAK-6883, FULL estimation compares segmentstore size with the previous FULL. There can be cases where the current segmentstore is smaller than the previous FULL (i.e. due to TAIL cleaning up more). This leads to FULL being skipped for much more than anticipated.

      A case to illustrate this scenario:

      Start Oak with a 10 GB repo
      GC #1: run FULL results in segmenstore of 20GB
      GC #2: run TAIL results in segmentstore of 11GB
      GC #3: run FULL (saturday) - skipped because the reference is 20GB from the previous FULL

      FULL be executed again only when the segmentstore grows back above 20GB, which might be too late.

      Estimation should take this situation into account this and take a better decision.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: