Details
-
New Feature
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Service Arch 2020-02-10, Service Arch 2020-02-24
Description
The simplest form of this involves adding a fireAndForget flag to the RemoteCommandRequest. Then, in the AsyncDBClient, we set the moreToCome flag on the OpMsgRequest and skip the _waitForResponse continuation and return either Status::OK or the error on an actual write(2) socket failure.
Attachments
Issue Links
- depends on
-
SERVER-45982 Separate RequestState concept from NetworkInterfaceTL::CommandState
-
- Closed
-