[SERVER-19979] Detect replset clock skew from electionids Created: 17/Aug/15  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: Kevin Pulo 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
related to DRIVERS-228 Use electionId to detect stale primar... Closed
related to SERVER-18280 ReplicaSetMonitor should use election... Closed
Assigned Teams:
Replication
Participants:

 Description   

A replset member can detect clock skew between itself and a newly elected primary by checking the timestamp in the newly-elected member's election id, and comparing that to the local time when the member has first noticed the other member becoming PRIMARY. This requires that there be a recent previous heartbeat (eg. < 10s ago) showing the other member in not-PRIMARY state.

This is motivated by replset clock skew > 30s having more effect now that election ids are being used to notice stale primaries.


Generated at Thu Feb 08 03:52:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.