[SERVER-71075] async_rpc errors should contain targeting information at HostAndPort granularity Created: 03/Nov/22 Updated: 29/Oct/23 Resolved: 05/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | George Wangensteen |
| 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 2022-11-14, Service Arch 2022-11-28, Service Arch 2022-12-12 | ||||||||
| Participants: | |||||||||
| Description |
|
The async_rpc responses today contain the HostAndPort a command was run on only if it completed successfully. We also need to include this information in error cases - if we ever attempted to send a command to a HostAndPort, API users may want to send cleanup work to that particular node in the future, depending on the command (i.e. killCursors/_killOperations).
Note that we should probably do some of this cleanup automatically in cases where we know it should be done - but this might require design of a more robust _killOperation operation. To re-host existing components, such as the ARS, that do their own cleanup, the API should expose this information for now. |
| Comments |
| Comment by Githook User [ 05/Dec/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |