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

Out of order commit and durable timestamps discovered in __hs_insert_record

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: In Progress
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      Storage - Ra 2022-01-24

      Description

      Summary

      The wt_hs_insert_updates function calls _hs_insert_record function after fixing the OOO timestamps of a particular update in the update chain. To verify that the OOO timestamps were modified to the correct values I added the following assert in the _hs_insert_record function. The WiredTiger patch succeeded, however, the MongoDB patch had a number of test failures.

      WT_ASSERT(session, tw->durable_stop_ts == WT_TS_NONE || tw->durable_stop_ts >= tw->durable_start_ts);
      

       This seems very strange.

      Scope:

      • Investigate why timestamps are OOO.
      • Write a python reproducer.
      • Fix the issue.
      • Run a MongoDB patch with the same assert in _hs_insert_record

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              siddhartha.mahajan Sid Mahajan
              Reporter:
              siddhartha.mahajan Sid Mahajan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: