Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-3183 [Blob GC] Improvements/tools for blob garbage collection
  3. OAK-3443

Track the start time of mark in GC

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • 1.0.22, 1.2.7, 1.3.7, 1.4
    • blob

    Description

      Similarly to what is done for a shared datastore in OAK-3360, the start time of the mark should be used as a reference for deletion of blobs in GC for 1.0.x. The problem is that in 1.0.x the mark iterated over the data store which could take a lot of time (many hours) and the buffer due to blobGcMaxAgeInSecs may get stale due to which data loss could happen.

      Attachments

        Issue Links

          is a clone of

          Sub-task - The sub-task of the issue OAK-3360 Tracking the start time of mark in GC for a shared datastore

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. OAK-3813 Exception in datastore leads to async index stop indexing new content

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

          Bug - A problem which impairs or prevents the functions of the product. OAK-3456 MongoBlobGCTest.gcLongRunningBlobCollection() fails

          • Major - Major loss of function.
          • Closed

          Activity

            People

              amitjain Amit Jain
              amitjain Amit Jain
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: