-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
1
-
Storage - Tora 2020-05-04
When reading the history store as part of verify, we do not have a consistent view of the underlying table. The history store can be modified while we are trying to verify, which is not ideal. WT-5541 tried addressing this by:
- take a transaction - we can't do that because some of the code that walks the history store is wrapped under WT_WITH_PAGE_INDEX
- hold a snapshot - that doesnt work because the history store walk can call search() on the history store cursor which refreshes the snapshot.
History store also doesn't follow the usual transaction semantics as the updates carry transaction-ids from the original commit to the data store. This also prevents us from reading as of a snapshot to get a consistent view. For now, we are reverting the changes using WT-5556.
We will use this ticket to find a better solution to this problem.
- duplicates
-
-
- Closed
-
- is duplicated by
-
WT-5609 Use snapshot isolation whenever we use history store cursors in verification
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-