[
https://issues.apache.org/jira/browse/OAK-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064265#comment-15064265
]
Alex Parvulescu commented on OAK-3804:
--------------------------------------
bq. Not sure about reversing the output of tarmkrecovery as your comment above
re. the example output is a bit confusing.
the {{flush}} call appends the latest revision at the end of the journal file:
{code}
r0
r1
r2
{code}
the {{tarmkrecovery}} prints candidates in the new to old older, last one being
the current {{head}}, in this example {{r2}}:
{code}
r4
r3
r2
{code}
this means that if you want to use the {{tarmkrecovery}} output as input for
{{check}} you need to add it to a journal file in the correct order (output
reversed), does that make more sense, or am I off?
> 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)
