Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-1769

Better cooperation for conflicting updates across cluster nodes

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mreutegg Marcel Reutegger
            mreutegg Marcel Reutegger

            Dates

              Created:
              Updated:

              Slack

                Issue deployment