Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6843

Review write conflict checking

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Storage - Ra 2020-12-28

      In durable history we allow update chains to be evicted a lot more aggressively, wiredtiger's write conflict checking is done on the update chain as far as I'm aware. Additionally I'm not sure how it will interact with things being written to the history store.

      I think its worth reviewing write conflict logic with regards to the eviction changes made in durable history and validating correctness. Adding python tests where applicable.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: