Convert a Standalone to a Replica Set

On this page

Overview

Procedure

Cloud Manager will no longer support Automation, Backup, and Monitoring for MongoDB 3.6 and 4.0 after August 30th, 2024. Please upgrade your MongoDB deployment or migrate to Atlas.

OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.: The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.

Overview

Cloud Manager provides the ability to convert a standalone instance to a replica set. When converted, the replica set will have the former standalone instance as its primary.

Procedure

In MongoDB Cloud Manager, go to the Deployment page for your project.

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

Go to the Processes page.

Click the Processes tab for your deployment.

The Processes page displays.

Select the Clusters view for your deployment.

Click the ... ellipses for the process and select Convert to Replica Set.

Enter the replica set name.

Enter the replica set name and click the Convert button.

Important

The replica set name is immutable once deployed. This setting corresponds to the _id replica configuration option.

Cloud Manager displays the Editing Replica Set view. The following steps describe the contents of each section in that view.

Configure Cluster-Wide Settings

The Replica Set Configuration section contains the following cluster-wide configuration settings. Settings whose values are grey and non-interactive are immutable.

Setting	Description
Replica Set Id	Enter the name of your replica set deployment. You cannot change this once set. This setting corresponds to the `_id` replica configuration option.
Auth Schema Version	Select the schema for storing the user for storing the user data for your deployment. If you are upgrading from a MongoDB version older than 3.0, MongoDB 3.0+ uses a different schema for user data than previous versions. For compatibility information, see the Security Changes in the MongoDB 3.0 release notes.
Feature Compatibility Version	Select the Feature Compatibility Version of the deployment. Cloud Manager displays this field if your deployment runs MongoDB version 3.4 or later.
Replica Set Settings	Displays an table of each process associated with the replica set. You can configure the MongoDB server version, data directory, and log path of each process.
Process Name	Hostname and port of a `mongod` process. This hostname can be a hostname, an FQDN, an IPv4 address, or an IPv6 address. Cloud Manager initially groups each process under the replica set name. Click the to the left of the replica set name to display all `mongod` processes in the replica set. Cloud Manager applies any settings configured for the replica set to all of its associated processes.
Version	Select the MongoDB server version of the `mongod` process. Version Select the MongoDB server version of the `mongod` process.
Data Directory	Specify the directory where the `mongod` process stores data files. This setting corresponds to the `storage.dbPath` `mongod` configuration file option. The Cloud Manager Automation must have file system permission to read, write, and execute all files and folders in the specified directory. Each `mongod` process must have its own database directory. If deploying multiple `mongod` processes on the same host, ensure each process has its own distinct directory.
Log File	Specify the full path to the `mongod` log file, including the log file name and extension. This setting corresponds to the `systemLog.path` configuration file option. The `mongod` must have permission to read and write to the specified file. For example, specifying `/var/log/mongodb/mongo.log` directs the `mongod` to store its logfile in `/var/log/mongodb/` as `mongo.log`. The `mongod` must have its own unique log file. If deploying multiple `mongod` processes to the same host, ensure each `mongod` has its own distinct logfile.

Configure each Replica Set Member.

Set any advanced configuration options for your MongoDB replica set.

Review the changes.

Review the details of the replica set. When ready, click the Save button.

Click Review & Deploy to review your changes.

Click Confirm & Deploy to deploy your changes.

Otherwise, click Cancel and you can make additional changes.

Back

Edit a Replica Set

Convert Replica Set to Sharded Cluster