[
https://issues.apache.org/jira/browse/OAK-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585733#comment-14585733
]
Chetan Mehrotra commented on OAK-2829:
--------------------------------------
[~egli]
Saw following exception while running trunk. Looks like getRevisionTimestamp
should use '-' instead of '_' for splitting
{noformat}
15.06.2015 05:19:22.810 *ERROR* [pool-6-thread-5]
org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job
execution of
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$4@2c1293b9
: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.jackrabbit.oak.plugins.document.JournalEntry.getRevisionTimestamp(JournalEntry.java:235)
at
org.apache.jackrabbit.oak.plugins.document.JournalGarbageCollector.gc(JournalGarbageCollector.java:126)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$4.run(DocumentNodeStoreService.java:630)
at
org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:105)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{noformat}
Further looking at {{JournalGarbageCollector}} ... it would be simpler if you
record the journal entry timestamp as an attribute in JournalEntry document and
then you can delete all the entries which are older than some time by a simple
query. This would avoid fetching all the entries to be deleted on the Oak side
> 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)
