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

Set oldest timestamp on startup of WiredTiger

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.4.1, 4.7.0
    • Component/s: None
    • Labels:
    • Story Points:
      8
    • Sprint:
      Storage - Ra 2020-07-13, Storage - Ra 2020-07-27, Storage - Ra 2020-08-10

      Description

      We experienced a scenario in MongoDB testing where a checkpoint/recovery timestamp is earlier than the checkpoint history store oldest timestamp in the metadata, which results in an error returned to MongoDB when setting the oldest and stable timestamps from the checkpoint/recovery timestamp.

      We reverted the commit of WT-5679 to unblock progress on SERVER-46678 while we investigate and understand the how and why of the scenario above.

      This ticket is to understand the failures in BF-17616 and HELP-16055 so that we can re-commit WT-5679 with any necessary fixes and/or changes. 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              luke.pearson Luke Pearson
              Reporter:
              tammy.bailey Tammy Bailey
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: