-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
ALL
-
(copied to CRM)
-
0
For a workload with many threads performing medium-sized writes (unlike SERVER-61909 where there is a single large transaction which cannot fit in cache), especially one with prepared transactions since those cannot be rolled back, we can end up in a scenario where eviction cannot make meaningful progress. The threads performing the writes are being co-opted into performing eviction and cannot return until sufficient eviction progress is made, so they can essentially all become stuck as a result.
- related to
-
SERVER-64982 Extended lack of availability caused by transactions
- Blocked
-
SERVER-44870 MongoDB to allow WiredTiger to return WT_ROLLBACK for all transactions
- Backlog
-
SERVER-61251 Ensure long running storage engine operations are interruptible
- Backlog