[SERVER-52951] Make ReshardingRecipientService transitions to kApplying, kStrictConsistency, and kDone update coordinator document Created: 19/Nov/20 Updated: 29/Oct/23 Resolved: 02/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2, PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-11-30, Sharding 2020-12-14 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
Currently, when the ReshardingRecipientService transitions to kStrictConsistency and kDone it does not update the coordinator document. They need to update the document in order for the ReshardingCoordinatorService's state machine to make progress. |
| Comments |
| Comment by Githook User [ 02/Dec/20 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message:
|