Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
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:
- Hyper-V Time Synchronization Doesn't Correct the System Clock in the Virtual Machine if it is more than 5 Seconds ahead of the Host Clock
- Ubuntu on Hyper-V: /var/log/syslog 'systemd: Time has been changed' message every 5 seconds
- Azure: MongoDB hangs up on shutdown
We should warn users against using MongoDB <3.4.6 on a system with known clock issues.
Attachments
Issue Links
- documents
-
SERVER-29102 WiredTiger does not rotate journal log files
-
- Closed
-
-
SERVER-29230 Journal files accumulating on ReplicaSet Secondary
-
- Closed
-
-
WT-3327 Checkpoints can hang if time runs backward
-
- Closed
-
- related to
-
DOCS-13090 Statement in production notes seems incorrect.
-
- Closed
-