[SERVER-7555] Do not veto election based on stale data for down members Created: 05/Nov/12 Updated: 31/Mar/23 Resolved: 18/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 2 |
| Labels: | elections | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | RPL 9 (09/18/15) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Say you have a replica set, X, Y, Z. X can reach Y and Z but Y cannot reach anyone. In this case, Y should not veto X's election, but neither should Y vote for X. An example of this is where Y has a DNS failure and cannot lookup X or Z. |
| Comments |
| Comment by Eric Milkie [ 18/Sep/15 ] |
|
In 3.1, the new election protocol does not use vetos so this situation can never occur. |