[
https://issues.apache.org/jira/browse/OAK-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064156#comment-15064156
]
Michael Dürig commented on OAK-3804:
------------------------------------
Yes this should work. I already spoke to [~tmueller] about this offline. You
can even pass a custom journal file to the {{check}} run mode through the
{{--journal}} option so you don't have to mess with the original one. The
journal has the most recent entries always last (at the end of the file). Not
sure about reversing the output of {{tarmkrecovery}} as your comment above re.
the example output is a bit confusing.
> 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)
