-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
The default for the mongod option --journalCommitInterval is either 30ms or 100ms, depending on your system configuration (see code). The documentation as it exists currently is misleading. Each of the following could at least use a footnote to that end:
source/core/journaling.txt:100 milliseconds. source/core/journaling.txt:group commits. By default, MongoDB performs a group commit every 100 source/core/journaling.txt:milliseconds: as a result MongoDB commits all operations within a 100 source/core/write-operations.txt: fundamental basis for write concern, there is an up-to 100 source/faq/developers.txt:every 60 seconds and commits the :term:`journal` every 100 source/faq/fundamentals.txt:Writes are physically written to the :doc:`journal </core/journaling>` within 100 source/reference/configuration-options.txt: *Default:* 100 source/reference/configuration-options.txt: value is 100 milliseconds. Lower values increase the durability of source/reference/glossary.txt: 100ms and this is configurable using the source/reference/mongod.txt: between journal operations. The default value is 100 milliseconds, source/release-notes/2.0.txt: specifying your own group commit interval. 100ms is the default (same as source/tutorial/recover-data-following-unexpected-shutdown.txt:<setting-journal>`. The journal writes data to disk every 100