-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: 8.0.13
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
v8.2, v8.0
-
Repl 2025-09-29, Repl 2025-10-13
-
(copied to CRM)
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The OplogWriterImpl holds on to an OperationContext throughout its lifetime, and this OperationContext will have a session after the first write is done. If a rollback occurs, that WT's session cache will have a stale epoch, and any future cursors from it will be leaked.
- is related to
-
SERVER-93389 WiredTigerSessionCache does not properly dispose of sessions released after rollback
-
- Closed
-
- related to
-
SERVER-110834 Catch leaked cursors in WiredTigerSessionCache
-
- In Code Review
-