[DOCS-4285] update mmapv1 configuration file option names Created: 03/Nov/14 Updated: 04/Mar/23 Resolved: 18/Nov/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.14, mongodb-3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 9 weeks ago | ||||||||
| Description |
|
http://docs.mongodb.org/manual/reference/configuration-options/ A number of mmapv1-specific configuration file options have been renamed to include "mmapv1" in the dotted name. The old names are still supported and will trigger a startup warning when used. Here's a list of the updated options:
Additionally, it is a warning to provide configuration options for a storage engine that is currently active. For example, if the heap1 storage engine is selected using the `--storageEngine=heap1` option, mongod will log an error at startup if it detects any mmapv1 options on the command line or in the configuration file. |
| Comments |
| Comment by Githook User [ 17/Dec/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 17/Dec/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Sam Kleinman (Inactive) [ 18/Nov/14 ] |
|
benety.goh, what about storage.journal.enabled according to this ticket it looks like we have storage.journal and storage.mmapv1.journal with related options. Will dig in further... |
| Comment by Githook User [ 05/Nov/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |