Trigger an Initial Sync for One Process
On this page
- 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.
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.
Considerations
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.
Trigger Initial Sync
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.
Tip
See also:
lastResync parameter in the Cloud Manager Automation configuration for MongoDB instances.