[SERVER-66569] Allow priority takeover without direct heartbeats from the current primary Created: 18/May/22  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-21452 heartbeat response from secondary sho... Closed
Assigned Teams:
Replication
Participants:

 Description   

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.


Generated at Thu Feb 08 06:05:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.