-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Live Restore
-
Storage Engines, Storage Engines - Persistence
-
SE Persistence - 2025-08-15
-
None
During the live restore project we added logic to WiredTiger to catch a potential avenue of database corruption. The logic prevents WiredTiger from starting up, without live restore options, when opened on a database that appears to have an in progress live restore. The relevant function call is:
__wt_live_restore_validate_non_lr_system.
Effectively we should exercise this code path in a python test and demonstrate it throwing an EINVAL error.
The steps to do so would be:
- Open a live restore on a database, and specify 0 background threads. This will create an in progress live restore that cannot finish.
- Close the database connection
- Reopen it without any live restore configuration and we should see the error.
- is related to
-
WT-15104 Apply bit encoding to "version" and "read version" in address cookie
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
WT-15085 ASAN heap-buffer-overflow in __meta_live_restore_to_meta
-
- Closed
-
-
WT-13429
Variable cfg marked as unused while used
-
- Closed
-
- mentioned in
-
Page Loading...