Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66376

Support stable_timestamp usage changes in WiredTiger

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      As part of WT-9186, wt_txn_validate_commit_timestamp is changing the way it validates the commit timestamp. Now that we don't have out-of-order timestamps, we can (correctly) compare the commit timestamp of the first update on the update chain with the stable timestamp, instead of the commit timestamp from (say) session->timestamp_transaction("commit_timestamp=...").

      There seems to be a non-zero amount of server fallout from this change, I've linked a patch build in the comments. This will need to be investigated/fixed before we can include this change in WT.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            will.korteland@mongodb.com Will Korteland
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: