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

Concurrent updates of ordered index in cluster may fail

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 0.20
    • Fix Version/s: None
    • Component/s: core
    • Labels:

      Description

      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.

        Attachments

        1. OAK-1717-IT.patch
          9 kB
          Davide Giannella

          Issue Links

            Activity

              People

              • Assignee:
                edivad Davide Giannella
                Reporter:
                mreutegg Marcel Reutegger
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: