[
https://issues.apache.org/jira/browse/OAK-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585832#comment-14585832
]
Stefan Egli edited comment on OAK-2829 at 6/15/15 12:09 PM:
------------------------------------------------------------
[~chetanm], thx for spotting! That {{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!
was (Author: egli):
[~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)
