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 "Andrei Dulceanu (JIRA)" <ji...@apache.org> on 2017/02/24 15:39:44 UTC
[jira] [Updated] (OAK-5837) Consistency check should log more
details when traversing a corrupt node
[ https://issues.apache.org/jira/browse/OAK-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dulceanu updated OAK-5837:
---------------------------------
Component/s: segment-tar
> Consistency check should log more details when traversing a corrupt node
> ------------------------------------------------------------------------
>
> Key: OAK-5837
> URL: https://issues.apache.org/jira/browse/OAK-5837
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Priority: Minor
> Fix For: 1.7.0, 1.8
>
>
> {{CheckRepositoryTestBase#corruptRecord}} corrupts a {{NODE}} record by writing random bytes inside. Currently when a corrupt node {{/z}} is traversed by the consistency check the traversal will fail with the following message {{Error while traversing /z: null}}. Most likely the corruption stems from an attempt to read an out of bounds segment reference [1]. The log message in {{ConsistencyChecker}} should be changed to include the root cause and the reason of the traversal failure.
> [1] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/Segment.java#L266
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)