-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Service Arch
-
Fully Compatible
-
Service arch 2020-04-20, Service arch 2020-05-04, Service arch 2020-05-18
When we create a RemoteCommandRequestOnAny in the ARS here, we might already have a client operation key in the command BSON. I think the way to fix this is to move the clientOperationKey logic out of the RemoteCommandRequest here and instead use an ARS-owned clientOperationKey that is added to the metadataObj ahead of time.
- is related to
-
SERVER-46255 establishCursors/AsyncRequestsSender can leave dangling request if interrupted
- Closed
- related to
-
SERVER-65329 Ensure cursors are not leaked when hedging reads
- Open
-
SERVER-63982 Complete TODO listed in SERVER-47261
- Open