[SERVER-45813] Modify AsyncDBClient/NetworkInterfaceTL to allow Fire and Forget Created: 28/Jan/20 Updated: 29/Oct/23 Resolved: 24/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2020-02-10, Service Arch 2020-02-24 | ||||||||
| Participants: | |||||||||
| 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. |
| Comments |
| Comment by Githook User [ 24/Feb/20 ] |
|
Author: {'username': 'cheahuychou', 'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com'}Message: |