-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Transactions
-
Fully Compatible
-
SE Transactions - 2026-12-04
-
None
-
None
-
None
-
None
-
None
-
None
-
None
WT-17698 changes the WiredTiger default of eviction_updates_trigger from 0 (automatic, half of eviction_dirty_trigger) to 95. The tests under jstests/noPassthrough/txns_cache_errors rely on the old behaviour (update pressure at about 10% of a 256MB cache pulling application threads into eviction, leading to rollback / TemporarilyUnavailable or the cache pressure aborter), so they fail on the 2026-11-13 WiredTiger drop patch (6af5c818e5e64c0007db5bd2).
Failing tests: temporarily_unavailable_error.js, active_transaction_aborted.js, transaction_too_large_for_cache.js.
Fix: explicitly set eviction_updates_trigger=0 in wiredTigerEngineConfigString for these tests. 0 keeps the previous automatic calculation, so this is safe on both the old and new WiredTiger.
Follow-up (not part of this ticket): WiredTigerCachePressureMonitor assumes updates trigger = dirty trigger / 2 when no value is configured, and the wiredTigerEvictionUpdatesMaxGB description says the same; both need revisiting if the new WT default is kept.
- is related to
-
WT-17698 Raise the default update eviction trigger
-
- In Code Review
-