[SERVER-68555] Add new RemoteCommandRunner ErrorExtraInfo and use it to store detailed error information Created: 04/Aug/22 Updated: 29/Oct/23 Resolved: 16/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2022-08-22, Service Arch 2022-09-05, Service Arch 2022-09-19 |
| Participants: |
| Description |
|
Add a new ErrorExtraInfo that the RemoteCommandRunner can use to store detailed error information in the case of RPC failure. Convert the RCR's error handling path to make use of this new EEI. After this ticket, the runner should return a future that will be set with a singleĀ ErrorCodes::RemoteCommandRunnerExecutionError error in the case of error. Any additional information about the underlying error (i.e. whether it was local or remote, write concern, etc) will be stored in the ErrorExtraInfo object. |
| Comments |
| Comment by Githook User [ 15/Sep/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |