jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-7728) Oak run check command fails with SegmentNotFound exception
Date Mon, 22 Oct 2018 12:08:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658920#comment-16658920

Michael Dürig commented on OAK-7728:

Looking at the output ([^check-output.txt]) there seems nothing wrong to me. AFAICS this is
just the tool reporting missing segments causing the respective revisions to be invalid.

[~ioancris], could you clarify whether the {{oak-run check}} failed with a {{SegmentNotFoundException}}
or whether the latter was reported by the tool. In the former case, do you have a stack trace
so we can determine wither this is a duplicate of OAK-7837? In the latter case I'd this is
not a bug but expected behaviour .

> Oak run check command fails with SegmentNotFound exception
> ----------------------------------------------------------
>                 Key: OAK-7728
>                 URL: https://issues.apache.org/jira/browse/OAK-7728
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: run, segment-tar
>    Affects Versions: 1.8.2
>            Reporter: Ioan-Cristian Linte
>            Assignee: Andrei Dulceanu
>            Priority: Major
>             Fix For: 1.10
>         Attachments: check-output.txt, we-retail-stage-corruption.log
> The check command for oak run fails with SegmentNotFound exception.
> See attach file for output.

This message was sent by Atlassian JIRA

View raw message