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
-
- Closed
-
-
SERVER-112656 Investigate if we can cache sessions after rts makes them sale
-
- Backlog
-