- Reference >
- Supported MongoDB Options for Automation
Supported MongoDB Options for Automation¶
On this page
Overview¶
The processes.<args>
object in an
automation configuration file
specifies the configuration options for each MongoDB instance. The
supported settings depend on the version of MongoDB.
MongoDB 2.6 and Later Configuration Options¶
The processes.args2_6
object applies to MongoDB versions 2.6 and
higher and supports the following MongoDB settings and parameters. The
object uses the
MongoDB configuration format.
The processes.args2_6
object supports the following:
basisTech.rootDirectory
-
If you set
net.bindIp
, you must include127.0.0.1
as well.Example
net.http.JSONPEnabled
MongoDB 3.6 removes the deprecated
net.http
settings. You cannot setnet.http
settings on MongoDB 3.6+ deployments.net.http.RESTInterfaceEnabled
MongoDB 3.6 removes the deprecated
net.http
settings. You cannot setnet.http
settings on MongoDB 3.6+ deployments.net.http.enabled
MongoDB 3.6 removes the deprecated
net.http
settings. You cannot setnet.http
settings on MongoDB 3.6+ deployments.replication.secondaryIndexPrefetch
setParameter.enableTestCommands
setParameter.newCollectionsUsePowerOf2Sizes
setParameter.textSearchEnabled
storage.repairPath
storage.journal.commitIntervalMs
storage.journal.enabled
storage.mmapv1.journal.debugFlags
storage.mmapv1.journal.commitIntervalMs
storage.mmapv1.preallocDataFiles
storage.mmapv1.nsSize
storage.nsSize
storage.preallocDataFiles
storage.quota.maxFilesPerDB
storage.quota.enforced
storage.smallFiles
Ops Manager 1.8.0 and later allow you to specify a custom option
using the setParameter.[other]
option.
With setParameter.[other]
, you specify both the parameter, and its
value, as in the following MongoDB configuration document: