[SERVER-57113] Use ShardingDDLCoordinator instead of ShardingDDLCoordinator_NORESILIENT in move primary Created: 21/May/21 Updated: 29/Oct/23 Resolved: 12/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2021-06-14, Sharding EMEA 2021-07-26 | ||||||||
| Participants: | |||||||||
| Description |
|
The MovePrimaryCoordinator is still using the old ShardingDDLCoordinator_NORESILIENT interface. The goal of this ticket is to integrate movePrimary with the new ShardingDDLCoordinator infrastructure. For the moment we won't make it resilient, so it won't persist its state on disk. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 12/Jul/21 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: ... instead of ShardingDDLCoordinator_NORESILIENT |
| Comment by Marcos José Grillo Ramirez [ 16/Jun/21 ] |
|
Pausing this task because it will be better to address SERVER-32531 as there are some tests that still use standalone mongod's as shards and then execute the movePrimary command. |