[SERVER-66326] Simplify cancellation flow in shard split donor service Created: 09/May/22 Updated: 29/Oct/23 Resolved: 11/May/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: | Matt Broadstone | Assignee: | Matt Broadstone |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-05-16 |
| Participants: |
| Description |
|
The ShardSplitDonorService currently has a few paths for emplacing the decision and completion promises, which makes it difficult to trace when stepdowns or explicit cancellations occur. This ticket will track the work to refactor the run method to set the promises from a single source. |
| Comments |
| Comment by Githook User [ 10/May/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |