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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/12/18 10:35:46 UTC

[jira] [Commented] (OAK-3804) Add tarmk revision recovery listing to oak-run

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

Michael Dürig commented on OAK-3804:
------------------------------------

Probably a good idea to have something like this for emergency recovery. We should also make it resilient against all sort of errors (like corrupted/missing tar files/segments). AFAICS currently it would just bail out in such cases. Optimally it would just print a warning and continue with what is there. 



> Add tarmk revision recovery listing to oak-run 
> -----------------------------------------------
>
>                 Key: OAK-3804
>                 URL: https://issues.apache.org/jira/browse/OAK-3804
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run, segmentmk
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>         Attachments: OAK-3804.patch
>
>
> There are cases where the flush thread apparently gets stuck (OAK-3303), this means that the journal file will not be updated resulting in loss of content as the journal file is the single source of truth.
> This oak run mode would be a best effort approach to parse the tar files and come out with (newer) candidates for root entries to the journal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)