-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
From siyuan.zhou@mongodb.com in SERVER-21452:
Given that priority takeover is based on heartbeats, if the secondary with higher priority cannot connect to the existing primary, it will never take over the primary, like in the following case.
P(priority: 2) <-> S(priority: 1) <-> S(priority: 3)
And this is not ideal.
- related to
-
SERVER-21452 heartbeat response from secondary should not schedule priority takeover
- Closed