[
https://issues.apache.org/jira/browse/OAK-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574434#comment-14574434
]
Stefan Egli edited comment on OAK-2829 at 6/5/15 12:46 PM:
-----------------------------------------------------------
Did some more TODO's from mentioned JournalEntry [in a fork on my github
account|https://github.com/eglistefan/jackrabbit-oak/tree/OAK-2829] and
[created a pull request|https://github.com/mreutegg/jackrabbit-oak/pull/1]:
* querying external changes in chunks
* use external sort when applying changes to diffcache
* push changes to memorydiffcache instead of localdiffcache
* handle external changes for recoveries
* clean up old journal entries
What's still left to do is also mentioned in the [JournalEntry on my
fork|https://github.com/eglistefan/jackrabbit-oak/blob/OAK-2829/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document/JournalEntry.java#L50]:
* add automated tests for some more cases
* integrate the JournalGarbageCollector
[~mreutegg], pls review and apply as applicable. Let's discuss next steps next.
was (Author: egli):
Did some more TODO's from mentioned JournalEntry [in a fork on my github
account|https://github.com/eglistefan/jackrabbit-oak/tree/OAK-2829] and
[created a pull request|https://github.com/mreutegg/jackrabbit-oak/pull/1].
[~mreutegg], pls review and apply as applicable. Let's discuss next steps next.
> 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)
