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

Concurrent updates of ordered index in cluster may fail

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • 0.20
    • None
    • core

    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

          relates to

          Bug - A problem which impairs or prevents the functions of the product. OAK-1185 DocumentNodeStore: annotate conflicts

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Task - A task that needs to be done. OAK-1730 Possible NPE in OrderedContentMirrorStoreStrategy

          • Major - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: