[jira] [Resolved] (OAK-1170) Inconsistent reads with concurrent benchmark tests

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-1170.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.12)
                   0.11

Fixed in http://svn.apache.org/r1541915

Changes:
- make external changes only visible in background read, based on _lastRev available on root document
- remove MongoNodeStore.publishRevision()
- adjust some tests because the implementation doesn't try to make external changes visible anymore on a conflict
- enable test added for this issue

> Inconsistent reads with concurrent benchmark tests
> --------------------------------------------------
>
>                 Key: OAK-1170
>                 URL: https://issues.apache.org/jira/browse/OAK-1170
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>             Fix For: 0.11
>
>
> Running concurrent benchmark tests with multiple Oak+MongoMK instances may lead to inconsistent reads. It may happen that a MongoMK instance reads child nodes at a given revision and then later finds out some of those children do not exist anymore at the same revision.



--
This message was sent by Atlassian JIRA
(v6.1#6144)