[
https://issues.apache.org/jira/browse/OAK-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978314#comment-13978314
]
Marcel Reutegger commented on OAK-1717:
---------------------------------------
OAK-1730 added a similar test as contained in the patch attached to this issue.
The test fails frequently on travis and I disabled it with a reference to this
issue in http://svn.apache.org/r1589440
> Concurrent updates of ordered index in cluster may fail
> -------------------------------------------------------
>
> Key: OAK-1717
> URL: https://issues.apache.org/jira/browse/OAK-1717
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 0.20
> Reporter: Marcel Reutegger
> Attachments: OAK-1717-IT.patch
>
>
> In a clustered deployment with DocumentNodeStore on MongoDB it may happen
> that concurrent updates on the new ordered index fail because of conflicts.
> A common use case is maintaining an ordered index on a last modified date.
> When nodes with such a date are added concurrently on multiple cluster nodes,
> then all of them will try to update the ordered index at one end of the key
> list. The DocumentNodeStore will perform a couple of retries but there is no
> guarantee that the cluster nodes will sync within that time frame or some
> other session conflicts yet another time.
> A possible workaround is to declare the index as asynchronous.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
