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

Loosen check during rollback_to_stable

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.9, 4.0.3, 4.1.3, WT3.2.0
    • Component/s: None
    • Labels:
    • Sprint:
      Storage Engines 2018-08-27
    • Backport Requested:
      v4.0, v3.6

      Description

      We're checking during rollback_to_stable that we roll back all the most recent changes to a given key. In other words, we don't skip some recent updates, then roll back some older ones.

      But in a MongoDB test exercising capped deletes, the assertion is firing in the _id index: we have a key that was inserted with a timestamp then removed without a timestamp. The rollback_to_stable assertion is complaining about rolling back the insertion without rolling back the remove (it's not smart enough to figure out that either way the key disappears from the index).

      Make a change so the assertion doesn't fire in this case (i.e., make it less strict unless assert=(commit_timestamp=always|key_consistent) is configured for the table.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                michael.cahill Michael Cahill
                Reporter:
                michael.cahill Michael Cahill
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: