[DOCS-13090] Statement in production notes seems incorrect. Created: 10/Oct/19 Updated: 30/Oct/23 Resolved: 06/Nov/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | John Page | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-investigating | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 4 years, 14 weeks ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
DescriptionThe statement " WiredTiger storage engine may experience checkpoint hangs on systems with unreliable clocks." seems to have little supporting evidence among our engineers. https://docs.mongodb.com/v4.0/administration/production-notes/#clock-synchronization Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 06/Nov/19 ] |
|
Thanks for your patience. Publishing master -> 3.2 now with the updates. |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'email': 'ravind.kumar@mongodb.com', 'name': 'Ravind Kumar'}Message: |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Ravind Kumar', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Ravind Kumar (Inactive) [ 11/Oct/19 ] |
|
I'm checking w/ the server DS team to confirm whether the NTP clock is required for sharded transactions. cc milkie Based on that answer I'll move forward, as I may not be able to simply nuke the entire section as originally planned. |
| Comment by Ravind Kumar (Inactive) [ 10/Oct/19 ] |
|
No worries, this seems a straightforward enough fix. I'll try to get to it before the end of the week. Thanks for raising it! |
| Comment by John Page [ 10/Oct/19 ] |
|
Was unaware of |
| Comment by Susan LoVerso [ 10/Oct/19 ] |
This seems very reasonable to me. The fix is in every latest point release now. |
| Comment by Ravind Kumar (Inactive) [ 10/Oct/19 ] |
|
So from the original docs ticket, I see > We should warn users against using MongoDB <3.4.6 on a system with known clock issues. So maybe this warning only really applies to 3.4.5 and earlier? As noted in Kevin Arhelger's comment in #mongodb-tech: > Non-monotonic system clock is known to cause problems; related tickets include We'd probably want to confirm with someone from storage (perhaps sue.loverso who worked on |