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

Restrict prepare_timestamp to be > stable, not >= oldest

    XMLWordPrintableJSON

Details

    Description

      Currently the prepare timestamp is checked for being >= oldest (and rounded up if necessary and thus configured) – this check should be against stable, since otherwise it's possible to commit before stable and that leads to data inconsistency.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-63166 Restrict prepare_timestamp to be > stable, not >= oldest

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. WT-8747 Reading between commit_timestamp and durable_timestamp can produce inconsistency

          • Blocker - P1 - Blocks development and/or testing work, production could not run.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-60037 Enable the ordered timestamp assertion in MongoDB

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              keith.bostic@mongodb.com Keith Bostic (Inactive)
              dholland+wt@sauclovia.org David Holland
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: