[SERVER-74695] Improve the readability of the movePrimary's cloning phase Created: 08/Mar/23 Updated: 29/Oct/23 Resolved: 27/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03 |
| Participants: |
| Description |
|
The cloning phase of the resilient movePrimary was not implemented using the same readability pattern used for other phases. The idea is to implement each phase by calling meaningful functions that hide all the complexity of individual operations as well as error handling. Reading the workflow must be clear and flowing, allowing the engineers to understand the semantics of the command without losing attention to low-level details. Ideally the entire workflow should be visible on one screen. |
| Comments |
| Comment by Githook User [ 27/Mar/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |