[jira] [Resolved] (OAK-6827) Consistency check fails with active deletions

["Amit Jain (JIRA)" <ji...@apache.org>]

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

Amit Jain resolved OAK-6827.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.10

Done with commits [1812483|http://svn.apache.org/viewvc?rev=1812483&view=rev], [1812484|http://svn.apache.org/viewvc?rev=1812484&view=rev], [1812485|http://svn.apache.org/viewvc?rev=1812485&view=rev], [1812486|http://svn.apache.org/viewvc?rev=1812486&view=rev]

> Consistency check fails with active deletions
> ---------------------------------------------
>
>                 Key: OAK-6827
>                 URL: https://issues.apache.org/jira/browse/OAK-6827
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: blob-plugins, lucene
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>             Fix For: 1.8, 1.7.10
>
>
> With active deletions of lucene blobs the consistency check fails if the revision cleanup has not removed the older revisions or has not been run.
> The solution discussed was to track the active deletions and ignore if the missing blob ids being reported by the consistency check are present in the tracked deletions. 
> Also, this active deletions would have to updated during DataStore GC to remove from active deletions the ids not included in the mark references phase because they have finally been collected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)