[
https://issues.apache.org/jira/browse/OAK-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064159#comment-15064159
]
Michael Dürig commented on OAK-3804:
------------------------------------
FTIW: here is how to run the {{check}} mode for most thorough checking:
{code}
java -Xmx4g -jar oak-run-*.jar --bin=-1 --deep --path=/path/to/segment-store
--journal=custom-journal.log
{code}
Note: I think the {{check}} mode doesn't work with an external data store. This
would need fixing.
> 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)
