jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Marth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-1471) Mod count in permission store requires cluster wide synchronization
Date Wed, 05 Mar 2014 12:09:46 GMT

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

Michael Marth updated OAK-1471:

    Priority: Critical  (was: Major)

> Mod count in permission store requires cluster wide synchronization
> -------------------------------------------------------------------
>                 Key: OAK-1471
>                 URL: https://issues.apache.org/jira/browse/OAK-1471
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Marcel Reutegger
>            Assignee: Tobias Bocanegra
>            Priority: Critical
>             Fix For: 0.19
> The current permission store implementation keeps a mod count property on some of the
nodes to detect changes and update/invalidate a cache when required. In general this introduces
a contention point when there are concurrent modifications of access control entries for a
given user. Those concurrent changes may introduce conflicts and commits may have to be retried
after a rebase. This still works somewhat OK when there is just a single oak instance, because
both segment and document store implementation will eventually fall back to locking and serialize
the commits. However, it does not work well in a cluster, unless we apply the same locking
cluster wide.
> See also discussion here:
> http://markmail.org/message/k64udmgc3ctaqmn2

This message was sent by Atlassian JIRA

View raw message