[SERVER-32867] Tie liveness to the ability to replicate Created: 23/Jan/18  Updated: 06/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-32828 Connection storm on Primary, no election Closed
is related to SERVER-5217 Replica set fail-over on high volume ... Backlog
Assigned Teams:
Replication
Participants:
Case:

 Description   

It's possible to have a node that reports itself as up, continues heartbeating, and thus can keep the primary from stepping down, even if that node is unable to replicate new ops. If a secondary node is unable to replicate ops, whether because of an issue local to the secondary or because of an issue on the primary that prevents the secondary from getting oplog entries off it, the secondary should not in any way keep the primary from stepping down, or prevent an election of a new primary.


Generated at Thu Feb 08 04:31:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.