Details
-
Bug
-
Status: Closed
-
Blocker - P1
-
Resolution: Fixed
-
None
-
None
-
8
-
Storage - Ra 2022-01-24
-
v5.0
Description
Summary
The wt_hs_insert_updates function calls _hs_insert_record function after fixing the OOO timestamps of a particular update in the update chain. To verify that the OOO timestamps were modified to the correct values I added the following assert in the _hs_insert_record function. The WiredTiger patch succeeded, however, the MongoDB patch had a number of test failures.
WT_ASSERT(session, tw->durable_stop_ts == WT_TS_NONE || tw->durable_stop_ts >= tw->durable_start_ts);
|
This seems very strange.
Scope:
- Investigate why timestamps are OOO.
- Write a python reproducer.
- Fix the issue.
- Run a MongoDB patch with the same assert in _hs_insert_record
Attachments
Issue Links
- is caused by
-
WT-7447 Fix the assert fire because onpage out of order update is not popped from the stack
-
- Closed
-