Navigation

Convert Config Servers to a Replica Set

Overview

Feature Availability

  • For deployments running MongoDB 3.2.4 or Later.
  • Requires Automation Agent version greater than 2.6.1.x (i.e. greater than 2.6.1).

In a sharded cluster, config servers store the metadata for the sharded cluster. For a sharded cluster to be fully operational, the config servers must be available and the metadata must be consistent across the config servers.

Beginning in MongoDB 3.2, config servers, that run the WiredTiger storage engine, can be deployed as replica sets. Running config servers as replica sets improves consistency and increases availability for the config servers.

Warning

If you have backup enabled and if you convert a sharded cluster’s config servers to a replica set, then Cloud Manager Automation can no longer use snapshots created before the conversion to restore the sharded cluster. Automation can only use snapshots created after the conversion.

For new sharded cluster deployments using MongoDB 3.2, Cloud Manager deploys config servers as a replica set.

For existing sharded cluster deployments that are not running config servers as replica sets, you can convert the config servers to replica sets.

You can manage config server replica sets just as you would any other replica set.

Prerequisites

  • Automation Agent version greater than 2.6.1.x.
    The Automation Agent version must be greater than 2.6.1.x (i.e. greater than 2.6.1).
  • MongoDB 3.2.4 or Later
    To convert the config servers to a replica set, the sharded cluster must be running MongoDB 3.2.4 or later versions. To upgrade the MongoDB version, see Change the Version of MongoDB.
  • Three Config Servers to Convert
    The sharded cluster must be running exactly three config servers to convert. After the conversion of the config servers to a replica set, you can add additional members to the config server replica set.
  • Write Permission for Parent Directory of dbPath
    The Automation Agent must have write permission on the parent directory of the dbPath of each config server.

Procedure

Note

During the conversion of the config servers to a replica set,

  • If the config servers use the MMAPv1 storage engine, Cloud Manager changes the storage engine to WiredTiger.
  • Cloud Manager creates temporary config servers, and automation eventually deletes these config servers after the conversion. However, if your Monitoring Agent should detect them at any point during the conversion, they will appear as unreachable hosts in your deployments list. After the conversion, you can safely delete them from the list. See Remove a Process from Management or Monitoring.
1

If you have not upgraded your sharded cluster to MongoDB 3.2.4 or later, do so now.

See Change the Version of MongoDB.

2

Click Deployment, then the Processes tab, then the Topology view.

3

For the sharded cluster, under the Members column, click 3 CONFIGS.

4

On the line listing the sharded cluster, click the ellipsis icon and select Convert Config Servers to Replica Sets.

5

Enter a name for the new replica set.

6

Enter the ports for the temporary config servers created during the conversion and click Upgrade.

During conversion, the process creates temporary config servers. These temporary config servers must be network accessible from all nodes in the cluster. During the procedure, specify distinct available ports for these temporary config servers.

7

Click Review & Deploy.

8

Click Confirm & Deploy.