-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: 2.2.4, 2.4.3, 2.5.0
-
Component/s: Replication
-
None
-
ALL
Consider a replica set with three nodes: A, B, C. 'A' is PRIMARY, 'B' and 'C' are SECONDARY.
If there is a network partition between 'A' and 'C', then:
- A is still PRIMARY because it can see a majority of the set
- C will start an election trying to become PRIMARY
- It can see a majority of the set
- It cannot see a primary
If, for whatever reason, 'B' allows 'C' to become PRIMARY, then the set will have two PRIMARY nodes until one of them is stepped down.
- is duplicated by
-
SERVER-8145 Two primaries for the same replica set
- Closed
- is related to
-
SERVER-9756 network partition where minority was primary and stayed primary
- Closed
- related to
-
SERVER-9283 lastHeartbeatRecv flaps between invalid and valid dates
- Closed