[
https://issues.apache.org/jira/browse/OAK-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-1769:
-------------------------------
Fix Version/s: (was: 1.3.6)
1.3.8
> Better cooperation for conflicting updates across cluster nodes
> ---------------------------------------------------------------
>
> Key: OAK-1769
> URL: https://issues.apache.org/jira/browse/OAK-1769
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, mongomk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Labels: concurrency, scalability
> Fix For: 1.3.8
>
>
> Every now and then we see commit failures in a cluster when many sessions try
> to update the same property or perform some other conflicting update.
> The current implementation will retry the merge after a delay, but chances
> are some session on another cluster node again changed the property in the
> meantime. This will lead to yet another retry until the limit is reached and
> the commit fails. The conflict logic is quite unfair, because it favors the
> winning session.
> The implementation should be improved to show a more fair behavior across
> cluster nodes when there are conflicts caused by competing session.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
