[DOCS-8682] Document replica set behavior related to system time changes Created: 26/Aug/16  Updated: 16/Mar/23  Resolved: 16/Mar/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: post-launch_mongodb-3.4

Type: Task Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Ravind Kumar (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 46 weeks, 6 days ago
Story Points: 1

 Description   

Since the introduction of PV1, we've become more dependent on the local time synchronization and clock adjustment. It'll be useful to document the replica set behavior in the event of time changes (including leap seconds) to help guide our users and properly set their expectations.



 Comments   
Comment by Sarah Olson [ 16/Mar/23 ]

Closing this out on the grounds that:

  • Details of this request are significantly outdated. 
  • Our documentation has evolved substantially since this request was made. 

Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree.

Comment by Stennie Steneker (Inactive) [ 26/Aug/16 ]

FYI, there's a general post on MongoDB and leap seconds which predates PV1: https://www.mongodb.com/blog/post/mongodb-and-leap-seconds.

Generated at Thu Feb 08 07:56:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.