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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/09/04 12:02:52 UTC

[jira] [Commented] (OAK-1447) Offline tool to repair MongoMK documents

    [ https://issues.apache.org/jira/browse/OAK-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121193#comment-14121193 ] 

Chetan Mehrotra commented on OAK-1447:
--------------------------------------

LastRev recovery tool added by [~mreutegg] in OAK-2074 provide some support in this area

> Offline tool to repair MongoMK documents
> ----------------------------------------
>
>                 Key: OAK-1447
>                 URL: https://issues.apache.org/jira/browse/OAK-1447
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Michael Marth
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>              Labels: production, resilience, tools
>             Fix For: 1.1
>
>
> For cases where the document semantics in Mongo that are created by Oak get corrupted to a point that Oak does not come up anymore (but MongoDB is still available), we should have a mechanism to fix those inconsistencies.
> Of course, one could use Mongo tools like cmdline or MongoHub to manually go in, but an automated approach would be preferable in the medium term.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)