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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/10/27 10:07:07 UTC

[jira] [Closed] (OAK-6550) Make BlobTracker snapshot process smarter

     [ https://issues.apache.org/jira/browse/OAK-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella closed OAK-6550.
---------------------------------

Bulk close for 1.7.10

> Make BlobTracker snapshot 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, 1.7.10
>
>
> 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)