[
https://issues.apache.org/jira/browse/OAK-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-1717:
----------------------------------
Fix Version/s: (was: 1.3.0)
1.3.1
Bulk move to 1.3.1
> 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
> Assignee: Davide Giannella
> Labels: concurrency
> Fix For: 1.3.1
>
> 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.3.4#6332)
