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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/09/26 14:40:20 UTC

[jira] [Updated] (OAK-4852) Conditional update with relaxed cache consistency

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

Marcel Reutegger updated OAK-4852:
----------------------------------
    Labels: scalability  (was: )

> Conditional update with relaxed cache consistency
> -------------------------------------------------
>
>                 Key: OAK-4852
>                 URL: https://issues.apache.org/jira/browse/OAK-4852
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core, documentmk
>            Reporter: Marcel Reutegger
>              Labels: scalability
>
> With multiple DocumentNodeStore instances in a cluster, the root document can become a bottleneck when many concurrent commits use it as a commit root.
> The DocumentStore API currently requires that all operations that update documents immediately reflect all changes from other cluster nodes. Either when returning the before Document or implicitly via a subsequent find or query operation that may be served from the cache.
> However, the DocumentNodeStore only needs to see external changes on the root node when it does a background read (or when it detects a collision). In almost all cases it would be fine with an update operation that does not immediately reflect external changes in the cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)