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

BlobIdTracker should not resurrect deleted blob ids in a clustered/shared setup after GC

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.0, 1.6.3, 1.8.0
    • Component/s: blob
    • Labels:
      None

      Description

      BlobIdTracker can resurrect deleted blob ids from a previous run when running in a clustered setup by also synchronizing blob references from other cluster/shared nodes which don't have information about the deleted blob ids.
      The effect of this is that when blob gc is executed again it identifies those ids as candidates and logs a warning when trying to delete them since they had already been deleted in the last gc execution.

      The locally tracked files at each of the instances should be purged after synchronizing with the datastore.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: