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

Do not assert timestamps when rolling back a prepared transactions

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 4.4.9, 5.0.3, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Execution Team 2021-08-23
    • Not Needed

      When aborting a prepared transaction, we unconditionally run assertions that the timestamps are well ordered. Because a prepared transaction (by constraint of the API) can only have a durable timestamp assigned on the configuration string of a WT_SESSION::commit_transaction call, this assertion is doomed to fail when the update chain is otherwise timestamped.

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: