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

commit and durability timestamps are not validated at transaction commit

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-04-18

    Description

      The WiredTiger code has not historically validated commit and durability timestamps at transaction commit if they were set before the transaction commit. That is, timestamps were validated when they were set, rather than always being checked at transaction commit. This could lead to the following sequence:

      1. a transaction setting the commit timestamp before the stable timestamp
      2. stable being moved past the commit timestamp
      3. the transaction committing

      Which would result in a transaction committing before the stable timestamp.

      This is fixed in WT-8990, but results in MDB patch build failures.

      This is a data consistency problem and deserves a reasonably high priority.

      Attachments

        Activity

          People

            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: