Docs Menu

Trigger an Initial Sync for One Process

Use Cloud Manager Automation to start an initial sync process on one or more MongoDB instances. This resynchronizes data stored on MongoDB nodes in clusters.

  • You can only resync secondary nodes.

    A node might become the primary between the time when you trigger a resync and when it runs. In this case, the MongoDB Agent waits for you to connect to the node manually and run the rs.stepDown() command.

  • You can only schedule one node in any given replica set to resync at a given time. While one node resyncs, the Cloud Manager disables the Resync option for all other nodes.

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

  2. If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

  3. If the Deployment page is not already displayed, click Deployment in the sidebar.

    The Deployment page displays.

2

Click the Processes tab for your deployment.

The Processes page displays.

3
4

Click the name of the deployment that contains the process to resync. Cloud Manager opens the deployment Overview.

5
  1. Find the node that you want to resync.

  2. Click the Actions dropdown for that node.

6
7
8
9

Cloud Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.

  2. If you want to make further configuration changes, click Cancel.

    Click Modify for the cluster to make additional changes.

See also:

lastResync parameter in the Cloud Manager Automation configuration for MongoDB instances.