[jira] [Comment Edited] (OAK-1254) Parallel execution of SimpleSearchTest fails with MongoMK

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

    [ https://issues.apache.org/jira/browse/OAK-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844151#comment-13844151 ] 

Marcel Reutegger edited comment on OAK-1254 at 12/10/13 10:05 AM:
------------------------------------------------------------------

Fixed several issues in http://svn.apache.org/r1549801.

- Branch commits previously set the _lastRev when it inserted a document. This is not correct, because _lastRev must only reflect visible commits. The _lastRev for new documents is now set after the branch is merged and done with the background write operation.
- Revision handling sometimes didn't take the merge commit revision into account, but was operating on the revision when the change was applied to the branch.
- A merge commit was using a single revision to make branch commits visible. This does not work correctly when changes in the branch overwrite previous changes in the branch. A merge commit now consists of multiple revisions. One for each branch commit to make them visible in the sequence they were applied to the branch.
- The revision when a node was last modified was not calculated correctly when the _lastRev from another cluster node isn't yet visible to the local cluster node. This what the simplified test is about in the previous comment. The test now succeeds and is enabled.

{{ConcurrentAddNodesClusterIT#addNodesConcurrent}} still fails sometimes and needs further investigation. I was also running the same test multiple times with MongoNodeStore and those test runs were all successful.


was (Author: mreutegg):
Fixed several issues in http://svn.apache.org/r1549801.

- Branch commits previously set the _lastRev when it inserted a document. This is not correct, because _lastRev must only reflect visible commits. The _lastRev for new documents is now set after the branch is merged and done with the background write operation.
- Revision handling sometimes didn't take the merge commit revision into account, but was operating on the revision when the change was applied to the branch.
- A merge commit was using a single revision to make branch commits visible. This does not work correctly when changes in the branch overwrite previous changes in the branch. A merge commit now consists of multiple revisions. One for each branch commit to make them visible in the sequence they were applied to the branch.
- The revision when a node was last modified was not calculated correctly when the _lastRev from another cluster node isn't yet visible to the local cluster node. This what the simplified test is about in the previous comment. The test now succeeds and is enabled.

{{ConcurrentAddNodesClusterIT#addNodesConcurrent}} still fails and needs further investigation. I was also running the same test multiple times with MongoNodeStore and those test runs were all successful.

> Parallel execution of SimpleSearchTest fails with MongoMK
> ---------------------------------------------------------
>
>                 Key: OAK-1254
>                 URL: https://issues.apache.org/jira/browse/OAK-1254
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 0.12
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>             Fix For: 0.14
>
>
> At some point in the benchmark run one MongoMK instance will fail to read a node created by another instance. The exception is very similar to *E1* reported in OAK-1204.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)