-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
None
-
Storage Engines, Storage Engines - Transactions
-
SE Transactions - 2025-11-07
-
3
We currently use the reconfigure API to manage operations such as picking up new checkpoints, stepping up, and stepping down. These operations are resource-intensive, as they involve reading and writing metadata. Additionally, our current implementation disables the eviction server while reconfiguration is in progress.
while (slot < max_entries && loop_count++ < conn->dhandle_count) {
/* We're done if shutting down or reconfiguring. */
if (F_ISSET_ATOMIC_32(conn, WT_CONN_CLOSING | WT_CONN_RECONFIGURING))
break;
This behaviour may stall both the eviction server and the reconfigure thread. If the reconfigure thread needs to perform eviction, it can become stuck since the eviction queue is empty, potentially resulting in a deadlock.
Temporarily allow eviction server to continue working for disagg when reconfigure is set.
- is related to
-
WT-15951 timing_stress_rec_before_wrapup never gets selected in test/model
-
- Closed
-
-
WT-15936 (disagg.mode=leader) test/format __reconcile (rec_write.c:341) assertion failure
-
- Closed
-
- related to
-
WT-15951 timing_stress_rec_before_wrapup never gets selected in test/model
-
- Closed
-
-
WT-15976 Temporarily disable verify in teardown for layered tests
-
- Closed
-
-
WT-15974 Revisit the API usage for reconfigure in disagg
-
- Needs Scheduling
-
-
WT-15819 test/format (disagg.mode=follower) MSAN use-of-uninitialized-value in PALite
-
- Closed
-
-
WT-15936 (disagg.mode=leader) test/format __reconcile (rec_write.c:341) assertion failure
-
- Closed
-