[ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196548#comment-16196548 ]
Amit Jain commented on OAK-6550: -------------------------------- The problem on my setup (SegmentNodeStore) is * Active deletion deleted the blob on 4th * Compaction since then is skipped because there isn't enough garbage to clean up * Running consistency check reports failure since, the reference to the actively deleted garbage still exists. It will continue to fail until the compaction finally deletes it. > Make BlobTracker snaphot process smarter > ---------------------------------------- > > Key: OAK-6550 > URL: https://issues.apache.org/jira/browse/OAK-6550 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-plugins > Reporter: Amit Jain > Assignee: Amit Jain > Fix For: 1.8 > > > Currently, the BlobTracker snapshot() process is scheduled (every 12 hours by > default) which synchronizes the local additions & deletions since last change > with the datastore and consequently other cluster nodes. > The process should be slightly improved to run the sync on every removal i.e. > either through : > * Blob GC > * Active Deletion > And add some heuristic (most likely time based) to skip an upcoming sync > cycle if it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)