You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/03/27 05:28:42 UTC

[jira] [Updated] (OAK-1769) Better cooperation for conflicting updates across cluster nodes

     [ https://issues.apache.org/jira/browse/OAK-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated OAK-1769:
---------------------------------
    Component/s:     (was: mongomk)
                 documentmk

> 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, documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>              Labels: concurrency, scalability
>
> 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.15#6346)