Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.
  • Reference >
  • Advanced Options for MongoDB Deployments

Advanced Options for MongoDB Deployments

On this page

Overview

The following mongod and mongos configuration options are available through the Ops Manager Advanced Options field when you deploy MongoDB. You select advanced options when deploying replica sets, sharded clusters, and standalone instances.

Advanced Options

The Ops Manager Advanced Options map to the MongoDB configuration options and parameters described here.

auditLog

basisTech

  • rootDirectory: basisTech.rootDirectory

net

net.http

  • nohttpinterface: net.http.enabled
  • jsonp: net.http.JSONPEnabled
  • rest: net.http.RESTInterfaceEnabled

net.ssl

processManagement

replication

security

security.kmip

setParameter

sharding

storage

  • syncdelay: storage.syncPeriodSecs

  • noprealloc: storage.mmapv1.preallocDataFiles

  • smallfiles: storage.mmapv1.smallFiles

  • nssize: storage.mmapv1.nsSize

  • quota: quota

  • quotaFiles: quotaFiles

  • directoryperdb: storage.directoryPerDB

  • engine: storage.engine

    New in version 3.4: You can set the engine option to inMemory to use an in-memory storage engine per member in your deployment.

    If a member using an in-memory storage engine fails or is shut down, it loses all of its data. When that member is restarted, it needs to resychronize all of the data from another member. You can use an in-memory storage engine for multiple members of a replica set or shard.

    For more information, see In-Memory Storage Engine in the MongoDB manual.

storage.journal

storage.wiredTiger.collectionConfig

storage.wiredTiger.engineConfig

storage.wiredTiger.indexConfig

storage.inMemory.engineConfig

systemLog