Some workloads see more transaction conflicts with WT_CURSOR::modify

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-11-13, Storage 2017-12-04
    • None

      We have noticed that since enabling the use of WT_CURSOR::modify via the MongoDB updateWithDamages interface, the number of write conflicts returned has increased significantly.

      A particular example is running a YCSB 50/50 read/update workload. The additional conflicts can lead to a reduced performance, since the operations need to be retried.

      We need to investigate why the number of conflicts increased, and hopefully reduce the occurrence.

        1. Screen Shot 2017-11-13 at 2.59.55 pm.png
          Screen Shot 2017-11-13 at 2.59.55 pm.png
          86 kB
        2. Screen Shot 2017-11-15 at 4.18.55 pm.png
          Screen Shot 2017-11-15 at 4.18.55 pm.png
          495 kB

            Assignee:
            Keith Bostic (Inactive)
            Reporter:
            Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: