-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: History Store
-
Storage Engines, Storage Engines - Persistence
-
SE Persistence - 2025-12-05
-
None
It is possible to leave extra entries in the HS which makes verify trip. The reproducer repro.py
works on this commit which is the latest on develop:
commit bd267722770f832b80608f67ba8565a4141166da (HEAD -> develop, origin/develop, origin/HEAD) Author: Will Korteland <korteland@users.noreply.github.com> Date: Thu Nov 27 11:52:40 2025 +1100
Do the following to repro:
python3 ../test/suite/run.py -p hs34 cat WT_TEST/test_hs34.0/verify.err
You should observe the following logs:
wt, file:tablehs34.wt, verify hs: [WT_VERB_DEFAULT][ERROR]: int __hs_verify_id(WT_SESSION_IMPL *, WT_CURSOR *, WT_CURSOR_BTREE *, uint32_t), 80: the associated history store key a was not found in the data store file:tablehs34.wt: WT_PANIC: WiredTiger library panic wt, file:tablehs34.wt, verify hs: [WT_VERB_DEFAULT][ERROR]: int __hs_verify_id(WT_SESSION_IMPL *, WT_CURSOR *, WT_CURSOR_BTREE *, uint32_t), 80: the process must exit and restart: WT_PANIC: WiredTiger library panic wt, file:tablehs34.wt, verify hs: [WT_VERB_DEFAULT][ERROR]: void __wt_abort(WT_SESSION_IMPL *), 29: aborting WiredTiger library
- is related to
-
WT-16148 Investigate why version cursor cannot access the HS entry
-
- Needs Scheduling
-
-
SERVER-87919 Stop taking unstable checkpoints during recovery for restore
-
- Open
-