-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Networking & Observability
-
ALL
-
Service Arch 2023-02-20
-
0
SERVER-47602 reported an issue with out-of-order processing of _killOperations for hedged reads. This could cause leaking of cursors created on mongod servers to serve hedged reads. This ticket should write a repro and fix the issue to avoid leaking cursors while hedging reads.
Edit: cancellation of any in-progress request is susceptible to this issue, even when not hedging.
- is related to
-
SERVER-46255 establishCursors/AsyncRequestsSender can leave dangling request if interrupted
- Closed
-
SERVER-47602 _killOperations for hedged reads can reach remote before original operation
- Closed
-
SERVER-90290 [v8.0] Do not hedge reads by default on nearest readPreference
- Closed
-
SERVER-47261 AsyncRequestSender should populate clientOperationKey
- Backlog