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

Improve GC scalability on TarMK

    XMLWordPrintableJSON

    Details

    • Type: Epic
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.8.0
    • Component/s: segment-tar
    • Labels:
    • Epic Name:
      TarMK GC scalability

      Description

      This issue is about making TarMK gc more scalable:

      • how to deal with huge repositories.
      • how to deal with massive concurrent writes.
      • how can we improve monitoring to determine gc health.
        • Monitor deduplication caches (e.g. deduplication of checkpoints)

      Possible avenues to explore:

      • Can we partition gc? (e.g. along sub-trees, along volatile vs. static content)
      • Can we pause and resume gc? (e.g. to give precedence to concurrent writes)
      • Can we make gc a real background process not contending with foreground operations?

      This issue is a follow up to OAK-2849, which was about efficacy of gc.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: