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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/03/02 12:47:18 UTC

[jira] [Updated] (OAK-2829) Comparing node states for external changes is too slow

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

Davide Giannella updated OAK-2829:
----------------------------------
    Fix Version/s: 1.4

> Comparing node states for external changes is too slow
> ------------------------------------------------------
>
>                 Key: OAK-2829
>                 URL: https://issues.apache.org/jira/browse/OAK-2829
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Blocker
>              Labels: scalability
>             Fix For: 1.2.3, 1.4, 1.3.2, 1.0.19
>
>         Attachments: CompareAgainstBaseStateTest.java, OAK-2829-JournalEntry.patch, OAK-2829-gc-bug.patch, OAK-2829-improved-doc-cache-invaliation.2.patch, OAK-2829-improved-doc-cache-invaliation.patch, graph-1.png, graph.png
>
>
> Comparing node states for local changes has been improved already with OAK-2669. But in a clustered setup generating events for external changes cannot make use of the introduced cache and is therefore slower. This can result in a growing observation queue, eventually reaching the configured limit. See also OAK-2683.



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