[DOCS-10562] Add warning about using WiredTiger with MongoDB <3.4.6 on systems with unreliable clock Created: 21/Jul/17  Updated: 30/Oct/23  Resolved: 22/Aug/17

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Kevin Adistambha Assignee: Allison Reinheimer Moore
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-29102 WiredTiger does not rotate journal lo... Closed
documents SERVER-29230 Journal files accumulating on Replica... Closed
documents WT-3327 Checkpoints can hang if time runs bac... Closed
Related
related to DOCS-13090 Statement in production notes seems i... Closed
Participants:
Days since reply: 6 years, 29 weeks, 6 days ago
Epic Link: DOCS: 3.6 Server

 Description   

Prior to WT-3327, WiredTiger checkpoints were sensitive to clock issues (e.g. going backward in time). This could result in difficult to diagnose stalling issues (e.g. SERVER-29102, SERVER-29230).

Some known examples of clock issues:

We should warn users against using MongoDB <3.4.6 on a system with known clock issues.


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