-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 7.0.6, 5.0.25, 6.0.14, 8.0.0
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
v8.0, v7.0, v6.0, v5.0
-
Execution Team 2024-09-02, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-11-11
-
200
We don’t release cursors if the WiredTigerSessionCache is shutting down (in rollback).
But then when the session gets released after rollback, and the session cache is no longer shutting down, we try to release a session with cursors that aren't closed.
This triggers an invariant that cursors must be all closed before releasing the session back into the cache.
- is caused by
-
SERVER-85167 Size storer can be flushed concurrently with being destructed for rollback
- Closed
- is related to
-
SERVER-93848 WiredTigerSessionCache::getSession() can read stale value of shutting-down state
- Closed
-
SERVER-96234 Fix wiredtiger session cache invariant during DISTINCT_SCAN execution
- Closed
-
SERVER-96807 Fix inequality check in releaseSession code
- Closed
- related to
-
SERVER-96701 Create new policy around interaction between WiredTigerSessionCache and shutting down
- In Progress