[SERVER-29099] liveness timeout is only rescheduled on replSetUpdatePosition commands Created: 05/May/17  Updated: 06/Dec/22  Resolved: 15/May/17

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

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29079 Unify liveness information between sp... Backlog
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

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.


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