Add a Shard to a MongoDB Cluster

Ops Manager v6.0 will EOL in January 2025. Upgrade to a higher Ops Manager version as soon as possible.

You can use Ops Manager to add a shard to a MongoDB sharded cluster.

Navigate to the Clusters view for your deployment.

If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
If it is not already displayed, click Deployment in the sidebar.

Click the Clusters view.

Click Modify on the cluster where you want to add a shard.

In the Member Configuration section, add a shard.

Expand SHARD SETTINGS.
Click Add a Shard to add mongod processes to the shard.
To add additional mongod processes to the shard, click the Add a Mongod link.

Review and update settings for the new shard as needed:

Setting	Description
Member	Select one of the following replica set member roles from the menu: `Default` A data-bearing member of the replica set that can become the primary and vote in elections. Arbiter A non-data bearing member of the replica set that can vote in elections. Corresponds to the `arbiterOnly` replica configuration option. Hidden A data-bearing member of the replica set that can vote in elections. Corresponds to the `hidden` replica configuration option. Delayed Hidden A data-bearing member of the replica set that can vote in elections. Corresponds to the `secondaryDelaySecs` and `hidden` replica configuration options.
Hostname	Select from the menu the host to which Ops Manager Automation deploys the replica set member. The menu only lists hosts under Ops Manager Automation. For complete documentation on adding servers to Ops Manager Automation, see Provision Servers for Automation. This hostname can be a hostname, an FQDN, an IPv4 address, or an IPv6 address.
Port	Specify the IANA port number for the `mongod` process. This setting corresponds to the `net.port` configuration file option. Defaults to `27017`. The `mongod` must have exclusive access to the specified port. If deploying multiple `mongod` processes to a single host, you must select a unique unused port for each process.
Votes	Specify the number of votes that the replica set member has during elections. This setting corresponds to the `votes` `mongod` replica set configuration option.
Priority	Specify the priority of the member during elections. Replica set members with a priority of `0` cannot become the primary and cannot trigger elections. This setting corresponds to the `priority` `mongod` replica set configuration option.
Delay	Specify the number of seconds "behind" the primary member this member should "lag". This setting corresponds to the `secondaryDelaySecs` `mongod` replica set configuration option.
Build Indexes	Specify `true` to direct the `mongod` to build indexes. This setting corresponds to the `buildIndexes` `mongod` replica set configuration option.
Tags	Specify the tag or tags associated to the replica set. This setting corresponds to the `tags` `mongod` replica set configuration option. For complete documentation on replica set tags, see Replica Set Tags

Click Save to add the new shard to the cluster.

Back

Convert Config Servers to Replica Set

Stop Managing and/or Monitoring

Navigate to the .css-h15tq0{font-style:normal;font-weight:700;}Clusters view for your deployment.

Click Modify on the cluster where you want to add a shard.

In the Member Configuration section, add a shard.

Review and update settings for the new shard as needed:

Click Save to add the new shard to the cluster.

Navigate to the Clusters view for your deployment.