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 "angela (JIRA)" <ji...@apache.org> on 2017/02/16 08:15:41 UTC

[jira] [Updated] (OAK-5685) CLONE - Tool to detect permission store inconsistencies

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

angela updated OAK-5685:
------------------------
    Parent Issue: OAK-5684  (was: OAK-865)

> CLONE - Tool to detect permission store inconsistencies
> -------------------------------------------------------
>
>                 Key: OAK-5685
>                 URL: https://issues.apache.org/jira/browse/OAK-5685
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Michael Marth
>            Assignee: angela
>            Priority: Minor
>              Labels: production, resilience, tools
>             Fix For: 1.3.9, 1.4
>
>
> 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.3.15#6346)