[DOCS-11030] Document maxAcceptableLogicalClockDrift parameter Created: 16/Nov/17  Updated: 29/Oct/23  Resolved: 20/Nov/17

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 3.5.9

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: consistency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 12 weeks, 2 days ago
Epic Link: DOCS: 3.6 Server

 Description   

--setParameter maxAcceptableLogicalClockDriftSecs

See:https://wiki.corp.mongodb.com/display/KERNEL/Params



 Comments   
Comment by Githook User [ 20/Nov/17 ]

Author:

{'name': 'kay', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-11030: maxAcceptableLogicalClockDriftSecs parameter
Branch: master
https://github.com/mongodb/docs/commit/e8f73b4267fcd3db3ada997d78ff6ed6c2be95a2

Comment by Misha Tyulenev [ 17/Nov/17 ]

--setParameter maxAcceptableLogicalClockDriftSecs . startup-only parameter, must be positive, default is 1year (in seconds). The value limits the difference between the current clusterTime and a new clusterTime. if newClusterTIme - currentClusterTime > the parameter's value the newClusterTime will be rejected.

Comment by Jack Mulrow [ 17/Nov/17 ]

jeffrey.allen Here's the section on this parameter from the causal consistency design doc: https://docs.google.com/document/d/1B_IeakOu1_hjKxtIOZl2V8yFRGQZ1bYOTEGiF4aNKp0/edit#heading=h.r1ls2jlrtzzv

Comment by Jeffrey Allen [ 17/Nov/17 ]

After digging through the Causal Consistency epic / documents, I'm having trouble locating definitive information on what this parameter is / does.

jack.mulrow, can you point to either a scope or design doc which might have some more information?

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