[DOCS-12495] 3.6 journal process docs, change to WT checkpointing not clear Created: 20/Feb/19 Updated: 29/Oct/23 Resolved: 15/Apr/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 3.6 |
| Fix Version/s: | 3.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Annette Morrissey (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
v3.6 and 4.0 |
||
| Participants: | |
| Days since reply: | 4 years, 43 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
DescriptionThe v3.6 docs on the Journal Process seem to suggest that the WT checkpoint interval has changed. v3.6 (and 4.0) docs state: Changed in version 3.6: MongoDB sets checkpoints to occur in WiredTiger on user data at an interval of 60 seconds. v3.4 docs on journal process show:
The actual change is that there is no longer a second scenario under which a checkpoint occurs. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 15/Apr/19 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 15/Apr/19 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 10/Apr/19 ] |
|
Author: {'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 08/Apr/19 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}Message: |