You were redirected from a different version of the documentation. Click here to go back.

Deploy a Sharded Cluster


Sharded clusters provide horizontal scaling for large data sets and enable high throughput operations by distributing the data set across a group of servers. See the Sharding Introduction in the MongoDB manual for more information.

Use this procedure to deploy a new sharded cluster managed by Ops Manager. Later, you can use Ops Manager to add shards and perform other maintenance operations on the cluster.

Unique Names for Deployment Items

Use unique names for the new cluster and its shards.


Replica set, sharded cluster, and shard names within the same group must be unique. Failure to have unique names for the deployment items will result in broken backup snapshots.


You must provision servers onto which to deploy, and Ops Manager must have access to the servers.


If you will run MongoDB Enterprise and provision your own Linux servers, then you must manually install a set of dependencies to each server before installing MongoDB. The MongoDB manual provides the appropriate command to install the dependencies. See the link for the server’s operating system:



Click Deployment.


Click the Add button and select New Cluster.


Configure the sharded cluster.

Enter information as required and click Apply.

The following table provides information for certain fields:

Auth Schema Version Specifies the schema for storing user data. MongoDB 3.0 uses a different schema for user data than previous versions. For compatibility information, see the MongoDB Release Notes.
Eligible Server RegExp Specifies the servers to which Ops Manager deploys MongoDB. To let Ops Manager select from any of your provisioned servers, enter a period (”.”). To select a specific set of servers, enter their common prefix. To use your local machine, enter the machine name.
Config Server Replica Set Name If you deploy a sharded cluster on MongoDB 3.2 or higher, the config servers deploy as a replica set. This field specifies the name for the replica set.
Member Options Configures replica set members. By default, each member is a voting member that bears data. You can configure a member as an arbiter, hidden, delayed, or having a certain priority in an election.
Index Configuration Creates a MongoDB index. For details, see Create Indexes.
Advanced Options

Configures additional runtime options. For option descriptions, see Advanced Options for MongoDB Deployments.

For managed deployments running MongoDB 3.0 or later, you can add the engine option in Advanced Options to set which storage engine to use. For information on storage engines, see Storage in the MongoDB manual.

New in version 3.4: You can set the engine option to inMemory to use an in-memory storage engine in your deployment. For more information, see In-Memory Storage Engine in the MongoDB manual.


All members of a replica set do not need to use the same storage engine. You can deploy a replica set with members that use a mix of storage engines, including the in-memory storage engine. 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.


Optional. Make changes before you deploy.

If needed, you can reconfigure processes and change the topology.

To modify settings for a MongoDB process:

  1. Click the Processes tab.
  2. On the line listing the process, click Modify.
  3. Make changes as desired and click Apply.

To move a process to a different server:

  1. Click the Servers tab.


    The colored bar on the right of each server indicates the replica set or sharded cluster to which the server belongs.

  2. Drag and drop the process to a different server.


Click Review & Deploy to review your changes.


Review and approve your changes.

Ops Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. Otherwise, click Cancel and you can make additional changes.