-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Execution Team 2024-11-25
We should look into creating a policy where a session can only be checked out from the WiredTigerSessionCache while we are not shutting down, and where we can only shut down when there are no outstanding sessions that have not been checked back into the session cache. This should simplify a lot of our behavior around shutdown, and prevent bugs caused by attempting to access the storage engine after it has been shut down (for example, if a recovery unit destructor tries to release its session back into the cache after the storage engine has been shut down).
- depends on
-
SERVER-97686 Create API that enables releasing a session from an operation context's recovery unit
- Open
-
SERVER-97689 Release WiredTigerSessions that would prevent shutting down with new session cache shutdown policy
- Open
- is related to
-
SERVER-93389 WiredTigerSessionCache does not properly dispose of sessions released after rollback
- Closed
-
SERVER-97686 Create API that enables releasing a session from an operation context's recovery unit
- Open