[SERVER-37903] Allow a node to override the cluster electionTimeoutMilis Created: 02/Nov/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alyson Cabral (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
In 2 DC disaster recovery, it would be great to allow the nodes physically far away in the DR DC to wait longer before calling an election. Example: cluster electionTimeoutMilis = 10000 (10 seconds) but DR nodes override that value with electionTimeoutMilis = 300000 (5 minutes) |
| Comments |
| Comment by Siyuan Zhou [ 05/Nov/18 ] |
|
Priority takeover shouldn't be affected by the per node election timeout since it's a whole replset behavior. Changing priority takeover timeout also increases the chance for it to race against the catchup takeover. We also need to consider the impact on all references of electionTimeout, for example, speeding up sync source selection when the node doesn't have one. |