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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/12/18 11:14:46 UTC

[jira] [Resolved] (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:all-tabpanel ]

Alex Parvulescu resolved OAK-3804.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.13

fixed with http://svn.apache.org/viewvc?rev=1720744&view=rev and http://svn.apache.org/viewvc?rev=1720745&view=rev

I think it's good enough for now, we can further improve based on feedback from people using this.

> 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
>             Fix For: 1.3.13
>
>         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)