[SERVER-9848] nonprimaries should assist to resolve multiple primary situation Created: 02/Jun/13  Updated: 05/Feb/16  Resolved: 16/Oct/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: Dwight Merriman Assignee: Unassigned
Resolution: Done Votes: 3
Labels: elections
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-8145 Two primaries for the same replica set Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

If a replica set somehow gets into a state where
there are two primaries, and the two primaries both see a majority of
the replica set but not each other, then neither steps down.

This happens because only the two primaries try to resolve the
situation (see Manager::noteARemoteIsPrimary). In the test, because
the primaries don't see each other, they both mistakenly think they
are the sole primary, and do nothing.

If some other machine in the replica set sees two other machines are a
primary, that machine does nothing to try to resolve the situation. It
does not send a step down command to either primary. See
Manager::msgCheckNewState().

See: https://groups.google.com/forum/?hl=en-US&fromgroups=#!topic/mongodb-dev/WA--aofOjQI



 Comments   
Comment by Eric Milkie [ 16/Oct/15 ]

All nodes now pass an election term among themselves to indicate when a new primary has been elected, when using election protocolVersion 1, used by new replSets in 3.1.9 by default.

Generated at Thu Feb 08 03:21:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.