[jira] [Comment Edited] (OAK-9518) Investigate reducing NodeStore access for permissions defined in immutable mounts

["Karolin Varner (Jira)" <ji...@apache.org>]

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

Karolin Varner edited comment on OAK-9518 at 1/20/22, 4:05 PM:
---------------------------------------------------------------

[~angela] So the mount represents some external data store like a segment store or some document store or something related, right?

Cache is being invalidated because there is likely some data that has been changed by some other host I assume so an updated version is reloaded instead of reusing the stale data in the cache for some end.

This ticket sounds like reloading permission info is necessary for RW mounts (probably because permissions are changing), but reloading permission info for RO mounts is not.

How come we're assuming the data in RO mounts can change (thus necessitating cache invalidation) but the permission info can not?


was (Author: JIRAUSER281109):
So the mount represents some external data store like a segment store or some document store or something related, right?

Cache is being invalidated because there is likely some data that has been changed by some other host I assume so an updated version is reloaded instead of reusing the stale data in the cache for some end.

This ticket sounds like reloading permission info is necessary for RW mounts (probably because permissions are changing), but reloading permission info for RO mounts is not.

How come we're assuming the data in RO mounts can change (thus necessitating cache invalidation) but the permission info can not?

> Investigate reducing NodeStore access for permissions defined in immutable mounts
> ---------------------------------------------------------------------------------
>
>                 Key: OAK-9518
>                 URL: https://issues.apache.org/jira/browse/OAK-9518
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, security
>            Reporter: Angela Schreiber
>            Assignee: Angela Schreiber
>            Priority: Major
>
> when running oak with additional immutable mounts, the permission provider will come with a composite {{MountPermissionStore}} that loads entries from the different mount points.
> while for the mutable default mount reading the latest permission data from the {{NodeStore}} is required whenever the cache gets invalidated, this is probably not needed for immutable mounts.
> the goal of the this improvement is to investigate if and under which circumstances repeated reads for the immutable mounts can/should be prevented and measure the impact on overall performance. this includes taking potentially huge amounts of permission entries into account and define boundaries in case such an improvement was beneficial for mounts with relatively few permissions.
> cc: [~rma61870@adobe.com]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)