[jira] [Commented] (OAK-1186) Parallel execution of ConcurrentReadAccessControlledTreeTest fails with MongoMK

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

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

Marcel Reutegger commented on OAK-1186:
---------------------------------------

As mentioned in the description, conflict annotation does not always work, because it may happen that the conflict is not yet there on rebase, but only when merge is called on the underlying storage.

Created OAK-1202 to persue the retry approach.

> Parallel execution of ConcurrentReadAccessControlledTreeTest fails with MongoMK
> -------------------------------------------------------------------------------
>
>                 Key: OAK-1186
>                 URL: https://issues.apache.org/jira/browse/OAK-1186
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: bench, core, mongomk
>    Affects Versions: 0.10
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>
> The is caused by concurrent creation of test content and the conflict it creates in the index. Every Oak test instance tries to create {{/oak:index/nodetype/:index/nt%3Afile}}, but only one will succeed. AFAICS there are two options how to handle this:
> - Implement conflict annotation (OAK-1185), though I'm not sure this will really work. On commit, the rebase happens first, when changes from the other Oak instance may not be visible yet. Then, the commit hook runs and perform another branch commit with the changes, which works fine. Only the last step fails, when MongoMK tries to merge the branch. This is the point when the conflict may be detected.
> - Implement a retry logic in MongoMK/NS



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