[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: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Days since reply: | 6 years, 29 weeks, 6 days ago | ||||||||||||||||||||||||
| Epic Link: | DOCS: 3.6 Server | ||||||||||||||||||||||||
| Description |
|
Prior to Some known examples of clock issues:
We should warn users against using MongoDB <3.4.6 on a system with known clock issues. |