[SERVER-42917] Flow Control should disregard faulty wall clock time readings during lag calculation Created: 20/Aug/19  Updated: 29/Oct/23  Resolved: 21/Aug/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.1, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-42906 lastCommitted wall clock time can be ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-08-26
Participants:

 Description   

If the lastCommitted wall clock time is greater than the last applied wall clock time on the primary due to SERVER-42906, these values should be disregarded. Flow Control should treat this situation similarly to how it addresses faulty sample readings.



 Comments   
Comment by Githook User [ 22/Aug/19 ]

Author:

{'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com', 'name': 'Maria van Keulen'}

Message: SERVER-42917 Ignore nonsensical wall clock readings in lag calculation

(cherry picked from commit 0dbb48618e221d378fa25e9a718ea1ee7fb74c4f)
Branch: v4.2
https://github.com/mongodb/mongo/commit/c48209d589770d22120072b69260907d481d1f48

Comment by Githook User [ 21/Aug/19 ]

Author:

{'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com', 'name': 'Maria van Keulen'}

Message: SERVER-42917 Ignore nonsensical wall clock readings in lag calculation
Branch: master
https://github.com/mongodb/mongo/commit/0dbb48618e221d378fa25e9a718ea1ee7fb74c4f

Generated at Thu Feb 08 05:01:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.