[
https://issues.apache.org/jira/browse/OAK-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079867#comment-16079867
]
Amit Jain commented on OAK-5908:
--------------------------------
Backported to 1.6 with http://svn.apache.org/viewvc?rev=1801413&view=rev
> BlobIdTracker should not resurrect deleted blob ids in a clustered/shared
> 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
> Fix For: 1.7.0, 1.8, 1.6.3
>
>
> BlobIdTracker can resurrect deleted blob ids from a previous run when running
> in a clustered setup by also synchronizing blob references from other
> cluster/shared 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.4.14#64029)
