[SERVER-29079] Unify liveness information between spanning tree and heartbeat updates Created: 04/May/17  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Matthew Russotto 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:
Duplicate
is duplicated by SERVER-29099 liveness timeout is only rescheduled ... Closed
Related
related to SERVER-31963 Remove code for replication protocol ... Closed
related to SERVER-29076 Replace all usage of heartbeat op tim... Backlog
related to SERVER-29078 Eliminate use of memberHeartbeatData ... Closed
is related to SERVER-34728 Heartbeats are used to advance replic... Closed
is related to SERVER-30716 Log whenever a node updates its view ... Backlog
Assigned Teams:
Replication
Participants:

 Description   

Right now we have multiple ideas of whether a node is up or down; one called _health and the other called stale. These affect each other in different ways depending on whether we are a primary, secondary, or arbiter. We should figure out what we really want and combine this in a clearer way.


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