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

Document the undefined behavior when a range truncate overlaps with inserts

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.9, 4.0.1, 4.1.1, WT3.2.0
    • Component/s: None
    • Labels:
    • Story Points:
      2
    • Sprint:
      Storage Non-NYC 2018-06-18, Storage Non-NYC 2018-07-02

      Description

      At the moment if a range truncate is started over a range of keys, and in parallel another transaction inserts a key into that range, the behavior is not well defined - a conflict may be detected or both transactions may be permitted to commit. If they do commit, then there is a crash and recovery runs, the result may be different than what was in cache before the crash.

        Attachments

        1. test_truncate04.py
          3 kB
          Michael Cahill

          Activity

            People

            Assignee:
            vamsi.krishna Vamsi Boyapati
            Reporter:
            alexander.gorrod Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: