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 "Amit Jain (JIRA)" <ji...@apache.org> on 2015/09/09 13:25:45 UTC
[jira] [Updated] (OAK-3184) Consistency checker for data/blob store
[ https://issues.apache.org/jira/browse/OAK-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Jain updated OAK-3184:
---------------------------
Attachment: OAK-3184.patch
Proposed patch with tests.
* Added a new method {{checkConsistency}} to {{MarkSweepGarbageCollector}} which returns the number of missing blobs in the blob/datastore which are still referenced.
* Logs the missing blob ids as well as the node from which referenced, currently only for DocumentMK. Need to further investigate how to get the node id for SegmentMK.
* Can be triggered by {{checkConsistency}} from the BlobGCMBean.
[~tmueller], [~chetanm] Can you please review.
> Consistency checker for data/blob store
> ---------------------------------------
>
> Key: OAK-3184
> URL: https://issues.apache.org/jira/browse/OAK-3184
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: blob
> Reporter: Amit Jain
> Assignee: Amit Jain
> Labels: resilience, tooling
> Fix For: 1.3.6
>
> Attachments: OAK-3184.patch
>
>
> Consistency checker for data/blob store to report any missing blobs which can result as a consequence of erroneous gc or extraneous factors.
> * Will report any missing blob ids
> * Path of nodes referring to those blobs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)