[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 ] Chetan Mehrotra updated OAK-2829: - Labels: docs-impacting scalability (was: scalability) > 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: docs-impacting, 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)
[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)
[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 ] Marcel Reutegger updated OAK-2829: -- Labels: scalability (was: candidate_oak_1_0 scalability) > 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.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)
[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 ] Marcel Reutegger updated OAK-2829: -- Fix Version/s: 1.0.19 Merged into 1.0 branch together with changes for OAK-3002: http://svn.apache.org/r1695297 > 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: candidate_oak_1_0, scalability > Fix For: 1.2.3, 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)
[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 ] Michael Marth updated OAK-2829: --- Issue Type: New Feature (was: Bug) > 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: New Feature > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: candidate_oak_1_0, scalability > Fix For: 1.2.3, 1.3.2 > > 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)
[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 ] Michael Marth updated OAK-2829: --- Issue Type: Improvement (was: New Feature) > 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: candidate_oak_1_0, scalability > Fix For: 1.2.3, 1.3.2 > > 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)
[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 ] Chetan Mehrotra updated OAK-2829: - Labels: candidate_oak_1_0 scalability (was: scalability) > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: candidate_oak_1_0, scalability > Fix For: 1.2.3, 1.3.2 > > 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Fix Version/s: 1.2.3 Merged into 1.2 branch: http://svn.apache.org/r1688649 > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: scalability > Fix For: 1.2.3, 1.3.2 > > 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Fix Version/s: (was: 1.3.1) 1.3.2 > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: scalability > Fix For: 1.2.3, 1.3.2 > > 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Attachment: OAK-2829-JournalEntry.patch As mentioned before, I would like to get rid of the path field in the TreeNode class to reduce the memory usage. See attached patch 'OAK-2829-JournalEntry.patch' for proposed changes. [~egli], WDYT? > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: scalability > Fix For: 1.3.1, 1.2.3 > > 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)
[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
]
Stefan Egli updated OAK-2829:
-
Attachment: OAK-2829-improved-doc-cache-invaliation.2.patch
New version of [^OAK-2829-improved-doc-cache-invaliation.2.patch] attached that
fixes a test regression buglet in {{DocumentNodeStoreTest}}
> 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: Bug
> Components: core, mongomk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Blocker
> Labels: scalability
> Fix For: 1.3.1, 1.2.3
>
> Attachments: CompareAgainstBaseStateTest.java, 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)
[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
]
Stefan Egli updated OAK-2829:
-
Attachment: OAK-2829-improved-doc-cache-invaliation.patch
Attached [^OAK-2829-improved-doc-cache-invaliation.patch] which is a suggestion
on how to avoid invalidating the entire document cache when doing a
{{backgroundRead}} but instead making use of the new journal: ie only
invalidate from the document cache what has actually changed.
I'd like to get an opinion ([~mreutegg], [~chetanm]?) on this first, I have a
load test pending locally which found invalidation of the document cache to be
the slowest part thus wanted to optimize this first.
Open still/next:
* also invalidate only necessary parts from the docChildrenCache
* junits for all of these
> 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: Bug
> Components: core, mongomk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Blocker
> Labels: scalability
> Fix For: 1.3.1, 1.2.3
>
> Attachments: CompareAgainstBaseStateTest.java, OAK-2829-gc-bug.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)
[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
]
Stefan Egli updated OAK-2829:
-
Attachment: OAK-2829-gc-bug.patch
[~chetanm], thx for spotting! Theat {{getRevisionTimestamp()}} was quite buggy
though, it also requires parseLong with a base 16.. I've attached
[^OAK-2829-gc-bug.patch] which contains the fix plus a dedicated junit method
that would have caught both issues. Can you pls review and apply accordingly?
Thx!
> 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: Bug
> Components: core, mongomk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Blocker
> Labels: scalability
> Fix For: 1.3.1, 1.2.3
>
> Attachments: CompareAgainstBaseStateTest.java, OAK-2829-gc-bug.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)
[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: (was: 1.3.0) 1.3.1 > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: scalability > Fix For: 1.3.1, 1.2.3 > > Attachments: CompareAgainstBaseStateTest.java, 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)
[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 ] Michael Marth updated OAK-2829: --- Labels: scalability (was: ) > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Labels: scalability > Fix For: 1.3.0, 1.2.3 > > Attachments: CompareAgainstBaseStateTest.java, 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Attachment: graph-1.png > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Fix For: 1.3.0, 1.2.3 > > Attachments: CompareAgainstBaseStateTest.java, 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)
[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 ] Julian Sedding updated OAK-2829: Attachment: CompareAgainstBaseStateTest.java A few weeks ago, while testing the migration of a CRX repository to a local MongoDB, I made some observations that may be related. I was working with a modified version of oak-upgrade that allows incremental (or repeated) copying of a JR2 repo into an Oak repo. During the second run, with an identical source repo, I noticed that a lot of time was spent in the commit hooks calculating diffs. In DocumentNodeState#compareAgainstBaseState(), I experimentally skipped the optimization for DocumentNodeState instances, thus falling back to the generic implementation in AbstractNodeState. For this specific case, where a large commit is compared with no or very few changes, this accellerated the commit hooks by a factor of ~10. I have tried to reproduce this in a synthetic benchmark, but there I only managed to produce a scenario that had comparable performance for both. So while I don't understand the exact parameters, I provide this input in the hope that it will be helpful in resolving this issue. I'll also attach the benchmark class. > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Fix For: 1.3.0, 1.2.3 > > Attachments: CompareAgainstBaseStateTest.java, 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Priority: Blocker (was: Major) > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Blocker > Fix For: 1.3.0, 1.2.3 > > Attachments: 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Fix Version/s: 1.2.3 > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.3.0, 1.2.3 > > Attachments: 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Attachment: graph.png > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.3.0 > > Attachments: 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Attachment: (was: graph.tiff.png) > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.3.0 > > > 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)
[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 ] Marcel Reutegger updated OAK-2829: -- Attachment: graph.tiff.png > 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: Bug > Components: core, mongomk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger > Fix For: 1.3.0 > > Attachments: graph.tiff.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)
