Navigation

Move a Cluster

Atlas supports moving M0+ single-region and M10+ multi-region clusters to new regions.

Considerations

Migration, Downtime and Performance Impact

Depending on the amount of data to migrate, migrations can take a significant amount of time. To maximize availability for a replica set, Atlas migrates one member at a time, starting with the secondary members first and then the primary.

Migration can affect performance if your primary is already reaching operational capacity: each newly migrated replica set member must perform an initial sync from the primary, adding to the operational load. Migrations can also affect performance if read preferences are set to read from secondaries: the replica set is down one secondary during the migration.

VPC Peering (AWS Only)

If you move a cluster out of a region that has a VPC (Virtual Private Cloud) peering connection, the moved cluster can no longer use that peering connection to communicate with servers in the VPC. Any other clusters with nodes remaining in the original region can continue to use the VPC peering connection.

You can create multiple VPC connections for each region, including a new VPC peering connection with the region to which you moved a cluster. However, Atlas does not support VPC peering connections between AWS regions.

Note

Cluster nodes moved out of a region can no longer inherit access rules from an AWS security group or IP whitelisted VPC CIDR blocks configured for the VPC peering connection. You must Add Entries to the Whitelist for all the virtual servers residing in the VPC. Cluster nodes remaining in the region are unaffected.

Move a Single-Region Cluster

Use the following procedure to move nodes to an M0+ single-region cluster:

Note

You cannot change the cloud provider of an M10+ cluster. You may change both the cloud provider and the region for M2 and M5 clusters if the desired cloud provider and region supports those instance types. You can only change the region of an M0 Free Tier cluster.

1

Go to the Clusters view.

Click the ellipses icon for the cluster that you want to move, then select Edit Configuration.

Alternatively, if you are already viewing the specific cluster, click Configuration.

2

In the Cloud Provider & Region view, select the desired new region for the new cluster.

For M0, M2, and M5 instance sizes, the available regions are a subset of the total supported regions for any given cloud service provider.

3

Click Confirm & Deploy.

Move a Multi-Region Cluster

Use the following procedure to move nodes to one or more regions in an M10+ multi-region cluster:

Note

Each node in the preferred and electable regions can participate in replica set elections and can become the primary as long as the majority of nodes in the replica set are available. The total number of electable nodes in the cluster, nodes that participate in elections, must be 3, 5, or 7.

1

Go to the Clusters view.

Click the ellipses icon for the cluster that you want to move, then select Edit Configuration.

Alternatively, if you are already viewing the specific cluster, click Configuration.

2

In the Cloud Provider & Region view, review the current multi-region configuration options.

For a given region, click the currently selected Region and pick a new region from the drop-down list. If you modify the Preferred region, the Atlas cluster calls for one or more elections to select a new primary in the selected region. See Test Failover for instructions on testing your application response to a replica set election before changing the Preferred cluster.

To change the number of nodes Atlas deploys to a given region, increase or decrease the Number of Nodes value. the total number of nodes across the Preferred region and all Electable regions must be an odd number.

3

Click Confirm & Deploy.