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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/05/28 17:54:02 UTC

[jira] [Updated] (OAK-1448) Tool to detect and possibly fix permission store inconsistencies

     [ https://issues.apache.org/jira/browse/OAK-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated OAK-1448:
-------------------------------

    Attachment: OAK-1448-2.patch

Slightly edited patch, collapsing the various execute methods in {{RepositoryManager}} into one by introducing the concept of a named management operation. 

> Tool to detect and possibly fix permission store inconsistencies
> ----------------------------------------------------------------
>
>                 Key: OAK-1448
>                 URL: https://issues.apache.org/jira/browse/OAK-1448
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Marth
>            Assignee: angela
>            Priority: Minor
>              Labels: production, resilience, tools
>             Fix For: 1.1
>
>         Attachments: OAK-1448-2.patch, OAK-1448_.patch
>
>
> I think we should prepare for cases where the permission store (managed as a tree mirrored to the content tree) goes out of sync with the content tree for whatever reason.
> Ideally, that would be an online tool (maybe exposed via JMX) that goes back the MVCC revisions to find the offending commit (so that have a chance to reduce the number of such occurences) and fixes the inconsistency on head.



--
This message was sent by Atlassian JIRA
(v6.2#6252)