[DOCS-532] Journaling Commit Interval Note - Behavior is altered when there are pending j:true GLE Created: 19/Sep/12  Updated: 30/Oct/23  Resolved: 02/Oct/12

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Minor - P4
Reporter: Adam Comerford Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MongoDB 2.0+


Issue Links:
Depends
Participants:
Days since reply: 11 years, 20 weeks, 1 day ago

 Description   

These two manual pages should mention that the commit interval of the journal is impacted by whether or not there are pending j:true getLastError calls:

http://docs.mongodb.org/manual/reference/glossary/#term-journal
http://docs.mongodb.org/manual/reference/configuration-options/#journalCommitInterval

See this section of the code:

 // commit sooner if one or more getLastError j:true is pending
                    sleepmillis(oneThird);

The configured commit interval is actually divided by 3 if there is a j:true GLE call pending.

This is documented on the wiki here:

http://www.mongodb.org/display/DOCS/Journaling#Journaling-CommitAcknowledgement

But should probably be noted here also:

http://www.mongodb.org/display/DOCS/Journaling+Administration+Notes



 Comments   
Comment by Sam Kleinman (Inactive) [ 02/Oct/12 ]

https://github.com/mongodb/docs/commit/190dd46acfdc3ae5c1ff10a6d5618dda759af144

Comment by Scott Hernandez (Inactive) [ 19/Sep/12 ]

https://groups.google.com/group/mongodb-user/browse_thread/thread/53198c08092204b8/3ec5174c221c9e47?lnk=gst&q=journal+commit+best+worst#3ec5174c221c9e47

Generated at Thu Feb 08 07:38:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.