We have a build failure floating around where this assertion is firing.
The general pattern that we're seeing is that we have a tombstone and a standard update in the chain, both marked with WT_UPDATE_RESTORED_FROM_DS but NOT marked with WT_UPDATE_HS. We try to insert the update into the history store only to find that the exact same value with a matching time pair already exists.
We found a code path where this happens and fixed it in WT-7595 however, that doesn't seem to be the root cause that we're seeing in the build failures.
The scope of this ticket is to identify the root cause and fix the issue.
- depends on
-
WT-7751 Add an assert to ensure we never select an update that has been written to the history store for data store
-
- Closed
-