-
Type: Bug
-
Resolution: Duplicate
-
Priority: Critical - P2
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
v6.0, v5.0, v4.4, v4.2
-
Execution Team 2022-07-11
-
(copied to CRM)
Currently the size storer uses its own separate wiredtiger session from the caller because the size storer's reads and writes are untimestamped and wiredtiger has the limit of not able to change the config of an existing transaction. As a result, when eviction could not find candidates to evict, we run into the deadlock with ourselves.
We might want to add timeout to the load function similar to flush, and then make the caller to retry to break out of the deadlock.
- duplicates
-
SERVER-60334 Avoid caching the cursor and session in WiredTigerSizeStorer
- Closed
- is related to
-
SERVER-60334 Avoid caching the cursor and session in WiredTigerSizeStorer
- Closed
- related to
-
SERVER-61097 SizeStorer can cause deadlocks with cache eviction
- Closed
-
SERVER-61116 Audit and add assertions against using multiple WT_SESSIONs on the same thread
- Backlog