[
https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194720#comment-16194720
]
Vikas Saurabh commented on OAK-6550:
------------------------------------
Follow up to previous comment - this is the warn noticed during blob store
consistency check:
{noformat}
06.10.2017 13:41:55.392 *INFO* [sling-oak-observation-41359]
org.apache.jackrabbit.oak.plugins.blob.MarkSweepGarbageCollector Number of
blobs present in BlobStore : [410869]
06.10.2017 13:41:55.392 *INFO* [sling-oak-observation-41359]
org.apache.jackrabbit.oak.plugins.blob.MarkSweepGarbageCollector Length of blob
ids file retrieved 28896382
06.10.2017 13:41:56.810 *INFO* [sling-oak-observation-41346]
org.apache.jackrabbit.oak.plugins.blob.MarkSweepGarbageCollector Consistency
check found [136002] missing blobs
06.10.2017 13:41:56.811 *WARN* [sling-oak-observation-41346]
org.apache.jackrabbit.oak.plugins.blob.MarkSweepGarbageCollector Consistency
check failure in the the blob store : DataStore backed BlobStore
[org.apache.jackrabbit.oak.plugins.blob.datastore.OakFileDataStore], check
missing candidates in file /tmp/gcworkdir-1507296968243/gccand-1507296968243
{noformat}
> 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)
