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

Ensure that tombstones generated in 4.4 don't resurrect in 4.2

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • None
    • None
    • None
    • 5
    • Storage Engines 2020-03-23

    Description

      There is a scenario where we are running with the changes to durable history when we write a value to the data file with a stop timestamp (if it's removed, but the remove isn't globally visible).

      If a user then starts using that database with MongoDB 4.2, I believe we ignore timestamps altogether, and thus the value will become visible again on startup.

      While writing this up, I've realised that rollback_to_stable on clean shutdown might fix this up - but we should confirm with testing in the least.

      Attachments

        Activity

          People

            keith.bostic@mongodb.com Keith Bostic
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: