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

MDB server sets the commit/durable timestamps equal to the stable timestamp

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-03-21, Execution Team 2022-04-04

    Description

      Generally, it is not correct to allow a transaction to commit with a commit timestamp at the stable timestamp, or a prepared transaction to commit with a durable timestamp at the stable timestamp. This can confuse checkpoint as to whether the newly committed transaction should be included in the checkpoint and can potentially lead to data inconsistencies.

      With the merge of WT-7712, WiredTiger standalone builds fail attempts to set the commit or durable timestamps to the stable timestamp, but MDB Server builds are allowed to do so.

      We do not know of any actual MDB Server problems in this area, but it would be good to fix any place where this happens and change the WiredTiger standalone behavior apply to all builds, to avoid the introduction of problems in the future.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: