[
https://issues.apache.org/jira/browse/OAK-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063784#comment-15063784
]
Alex Parvulescu commented on OAK-3804:
--------------------------------------
Example output:
{code}
Store repository/segmentstore
Current head revision 6e2363ba-e7de-4374-a01c-ef7032ef6efa:244148
b1e12a3f-e42e-46cd-a44e-2968629ba83c:261788
b1e12a3f-e42e-46cd-a44e-2968629ba83c:261488
905c5697-d1da-4c43-a23f-80e56db4d21e:261788
905c5697-d1da-4c43-a23f-80e56db4d21e:261604
905c5697-d1da-4c43-a23f-80e56db4d21e:261568
6e2363ba-e7de-4374-a01c-ef7032ef6efa:244540
6e2363ba-e7de-4374-a01c-ef7032ef6efa:244148
{code}
listing is from latest to oldest (last one being the current head state from
the journal). You'd need to pick one by one going down the list and setting the
journal head to this value.
> 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)
