[jira] [Commented] (OAK-6550) Make BlobTracker snaphot process smarter

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194571#comment-16194571 ] 

Vikas Saurabh commented on OAK-6550:
------------------------------------

[~amjain], just for heads up - one of my team member reported that blob store consistency check also feels bad about active deletion removing blobs behind its back. Btw, at this time, it is just a guess that consistency check logging warn for missing blobs is due to active deletion (but, that surely is the most likely candidate)... 

> 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)