[SERVER-45116] replSetStepDown attempts to hand off election to highest priority node Created: 12/Dec/19 Updated: 06/Dec/22 Resolved: 10/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
There are certain scenarios where priority takeover never succeeds. For example, if a user has 3 nodes in the main datacenter and 2 nodes in the backup datacenter. They want to move the primary from the main datacenter to the backup datacenter, so they raise the priority of a node in the backup datacenter. However, the nodes in the backup datacenter are always behind the main datacenter, so they can never win an election. A proposed fix to this is to let replSetStepDown accept a suggested next primary. When the command waits for a majority of nodes to catch up, it also waits for the suggested next primary to catch up. It then sends the replSetStepUp command to the suggested next primary. |
| Comments |
| Comment by Evin Roesle [ 10/Feb/20 ] |
|
Closing this project as Won't Do. If you would like to elect a specific node, please utilize the replSetFreeze command to freeze the nodes that you do not want to elect and then run the replSetStepDown command. If this is not a suitable solution, please reopen this ticket. |
| Comment by Siyuan Zhou [ 30/Jan/20 ] |
|
To follow up on the first issue tess.avitabile pointed out. |
| Comment by Tess Avitabile (Inactive) [ 30/Jan/20 ] |
|
Summary of discussion with evin.roesle, siyuan.zhou, and judah.schvimer:
|
| Comment by Tess Avitabile (Inactive) [ 02/Jan/20 ] |
|
A Replication team member suggested that instead of letting the user suggest the next primary, the stepping down node should use the highest-priority node as the suggested next primary. |