[SERVER-67456] Create skeleton implementation for free function that remotely invokes IDL commands Created: 22/Jun/22 Updated: 29/Oct/23 Resolved: 12/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Erin McNulty |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2022-07-11, Service Arch 2022-07-25 |
| Participants: |
| Description |
|
In this ticket, create a free function that accepts an IDL-defined command type and an operation context and executor. The function should remotely invoke (i.e. send) the command to a (for now) hard-coded host, and return a future to the user that will be set with the response received for the command or set with an error. For now, the targeted host can be hard-coded or use a localhost targeter, and no retry logic or error processing logic needs to be implemented. This will serve as the 'core'/skeleton of the part of the async-remote-command-running API, and we will add retry logic, more complex targeting capabilities, more sophisticated error processing etc later. To test this, consider using the NetworkInterfaceMock infrastructure to write unittests. |
| Comments |
| Comment by Githook User [ 08/Jul/22 ] |
|
Author: {'name': 'Erin McNulty', 'email': 'erin.mcnulty@mongodb.com', 'username': 'erin2722'}Message: |