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 2015/08/12 14:54:46 UTC
[jira] [Resolved] (OAK-3221) JournalTest may fail on machine with
slow I/O
[ https://issues.apache.org/jira/browse/OAK-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved OAK-3221.
-----------------------------------
Resolution: Fixed
Fixed in 1.0 branch: http://svn.apache.org/r1695498
The in-memory implementation is now used for this particular test.
> JournalTest may fail on machine with slow I/O
> ---------------------------------------------
>
> Key: OAK-3221
> URL: https://issues.apache.org/jira/browse/OAK-3221
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.0.19
>
>
> [~reschke] reported a failure for JournalTest.lastRevRecoveryJournalTestWithConcurrency() on a test machine without an SSD.
> This test creates 200 threads running lastRev recovery concurrently. Each thread will create a map using MapFactory. The default implementation in 1.0 is backed by MapDB and therefore creates quite a bit of I/O. Even on my machine with an SSD the test takes 11 seconds to run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)