-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
ALL
-
Security 2020-04-06, Service Arch 2021-07-12, Service Arch 2021-08-09, Service Arch 2021-08-23, Service Arch 2021-11-01, Service Arch 2021-11-15
-
1
When we cancel async operations in the Session here, we rely on the socket or baton to enforce full cancelation. We should add an additional reference atomic to force level triggering on cancelation (and maybe avoid baton contention as well).
- is related to
-
SERVER-61192 Session cancellation should interrupt blocking I/O
- Closed
-
SERVER-61197 Canceling a session should await completion of its operations on the baton
- Closed
- related to
-
SERVER-47166 Self-deadlock when cancelling networking sessions
- Closed
-
SERVER-48396 SIGUSR2 stack collection closes connections
- Closed
-
SERVER-61199 Complete TODO listed in SERVER-47229
- Closed