-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
8
-
Storage - Ra 2020-06-15, Storage - Ra 2020-06-29
Writing out of order timestamps to the history store causes visibility problems that are difficult to resolve. There are very few cases in MongoDB where they can use timestamps out of order. We should be able to keep the out of order content in cache until the section of the update chain that is out of order becomes globally visible and can be discarded.
That's only going to be OK if the content isn't between the stable and oldest timestamps. i.e: checkpoint doesn't need to flush the content that has a range of out of order timestamps.
- is depended on by
-
WT-6409 Fix failure due to assertion during rollback to stable
- Closed
- related to
-
SERVER-48603 Rollback via refetch can result in out of order timestamps
- Closed
-
SERVER-48772 Dropping multiple indexes incorrectly timestamps writes
- Closed
-
SERVER-48771 Enforce constraints on "multi-timestamp" transactions
- Closed