[DOCS-1416] --journalCommitInterval default value misleading Created: 20/Apr/13 Updated: 30/Oct/23 Resolved: 24/Apr/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 43 weeks ago |
| Description |
|
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:
|
| Comments |
| Comment by auto [ 24/Apr/13 ] |
|
Author: {u'date': u'2013-04-24T13:31:13Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 24/Apr/13 ] |
|
Author: {u'date': u'2013-04-24T13:31:13Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by J Rassi [ 20/Apr/13 ] |
|
The commit interval default will be 100ms if the containing filesystem for the data directory is associated with the same block device as the containing filesystem for the journal directory. Otherwise, it will be 30ms. ("Partition" is a misnomer in the code here – the correctness of that term breaks down, for example, if you're running off a single disk that isn't partitioned at all, or if you have LVM configured to run data/journal off of separate logical volumes backed by a device associated with a single disk partition) |
| Comment by Ed Costello [ 20/Apr/13 ] |
|
Could you confirm that the decision for 30 vs 100ms is based on whether the journal is on the same partition as (I'm guessing, I didn't read too far back in the code) the database files? |