[DOCS-10802] Mention that running WiredTiger with nojournal will force a checkpoint for every journal sync Created: 18/Sep/17 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Adistambha | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7, docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
Currently the Journaling and the WiredTiger Storage Engine page does not mention the effect on WiredTiger if MongoDB is started with the nojournal option. One of the effect is every journal sync will become a checkpoint instead to satisfy durability requirement. Since the journal was designed with quick sync in mind, the forced checkpoints could lead to slower performance when durability is required such as in a replica set. Reference (MongoDB 3.4.9): https://github.com/mongodb/mongo/blob/r3.4.9/src/mongo/db/storage/wiredtiger/wiredtiger_session_cache.cpp#L242-L249 |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |