[SERVER-69592] Solidify executor semantics for async command runner Created: 12/Sep/22 Updated: 29/Oct/23 Resolved: 14/Oct/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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service Arch 2022-10-17 | ||||||||
| Participants: | |||||||||
| Description |
|
Right now, the remote command running API accepts an ExecutorPtr as input which it uses to perform the asynchronous work. The shutdown of this executor is the only case presently when a non-RemoteCommandExecutionError can be returned by the API.
The purpose of this ticket is to investigate the tradeoffs between these options, discuss them with stakeholders, and make a decision as to the executor semantics for this API. Then update this ticket description with the conclusion, and make any required code changes.
Update after 6WR: We're going to have the API obey the contract that it always returns ErrorCodes::RemoteCommandExecutionError; it will re-write executor shutdowns to such an error and contain the originating error information in the EEI.
|
| Comments |
| Comment by Githook User [ 07/Oct/22 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |