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.
- is depended on by
-
SERVER-46678 Preserve durable history across restarts
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
WT-6537 Failed: compatibility-test-for-releases on Compatibility tests [WiredTiger (develop) @ 4854cf55]
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
WT-6391 Improve set_timestamp API to ensure consistent stable and oldest usage.
-
- Backlog
-