Critical Description
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
Attachments
Attachments
Issue Links
- is blocked by
-
OAK-1504
Create benchmark tests to measure effect of mod_count and everyone cache
-
- Closed
-