Restrict prepare_timestamp to be > stable, not >= oldest

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Execution Team 2022-02-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The WiredTiger drop incorrectly bounds the prepare timestamp at >= oldest, when the correct bound is > stable.

      This is a potential data consistency error.

      The WiredTiger ticket is WT-8745.

      The patch build is here: https://spruce.mongodb.com/version/61f88392a4cf476b5c07c14a/tasks

      Running a patch build on the change produces one consistent error, noPassthrough fails, but there's no obvious error in the output.

      Can someone please help us investigate this problem? – Thanks!

              Assignee:
              Josef Ahmad
              Reporter:
              Keith Bostic (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: