You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2017/03/08 05:39:38 UTC

[jira] [Created] (OAK-5908) BlobIdTracker should not resurrect deleted blob ids in a clustered setup after GC

Amit Jain created OAK-5908:
------------------------------

             Summary: BlobIdTracker should not resurrect deleted blob ids in a clustered setup after GC
                 Key: OAK-5908
                 URL: https://issues.apache.org/jira/browse/OAK-5908
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: blob
            Reporter: Amit Jain
            Assignee: Amit Jain


BlobIdTracker can resurrect deleted blob ids from a previous run when running in a clustered setup by also synchronizing blob references from other cluster 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)