-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
ALL
We cancel and reschedule the liveness timeout when we receive replSetUpdatePosition commands. We update liveness information on heartbeats as well, but don't cancel and reschedule the liveness timeout. There does not seem to be a reason for this inconsistency; we should either always reschedule it, or never reschedule it until we timeout and check if we need to step down.
- duplicates
-
SERVER-29079 Unify liveness information between spanning tree and heartbeat updates
- Backlog