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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/11/03 15:08:58 UTC
[jira] [Resolved] (OAK-5059) DocumentCachingDataStoreStatsTest
sometimes stuck
[ https://issues.apache.org/jira/browse/OAK-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved OAK-5059.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5.13
The problematic test is VersionGCWithSplitTest. It does not dispose the fixture after the test.
Fixed in trunk: http://svn.apache.org/r1767901
> DocumentCachingDataStoreStatsTest sometimes stuck
> -------------------------------------------------
>
> Key: OAK-5059
> URL: https://issues.apache.org/jira/browse/OAK-5059
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: it
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.6, 1.5.13
>
> Attachments: unit-tests.log, unit-tests.log
>
>
> The test sometimes gets stuck when it starts on an existing MongoDB with data that was written with a Virtual clock. The log then writes a WARN message like this:
> {noformat}
> 14:01:57.823 WARN [main] DocumentNodeStore.java:2136 Detected clock differences. Local time is 'Thu Nov 03 14:01:57 CET 2016', while most recent external time is 'Thu Nov 03 15:00:00 CET 2016'. Current _lastRev entries: [r1582a7d3d6b-0-1]
> 14:01:57.826 WARN [main] DocumentNodeStore.java:2143 Background read will be delayed by 3482,8 seconds. Please check system time on cluster nodes.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)