Start an initial sync for a cluster or process.
The MongoDB Agent checks whether the specified timestamp is later than the time of the last resync, and if confirmed, the MongoDB Agent:
Starts the initial sync on the secondary nodes in a rolling fashion
Waits until you ask the primary node to become the secondary with the rs.stepDown() method
Starts the initial sync on the primary node
Warning: Use this method with caution. During initial sync, Automation removes the entire contents of the node’s dbPath directory.
To learn more, see: https://docs.mongodb.com/manual/tutorial/resync-replica-set-member/
Syntax
mongocli cloud-manager clusters resync <clusterName> [options]
Arguments
Name | Type | Required | Description |
|---|---|---|---|
clusterName | string | true | Name of the cluster for which you want to start a resync. |
Options
Name | Type | Required | Description |
|---|---|---|---|
--force | false | Flag that indicates whether to skip the confirmation prompt before proceeding with the requested action. | |
-h, --help | false | help for resync | |
--processName | strings | false | Unique identifier for the host of a MongoDB process in the following format: {hostname}:{port}. |
--projectId | string | false | Hexadecimal string that identifies the project to use. This option overrides the settings in the configuration file or environment variable. |
--timestamp | string | false | Timestamp in ISO 8601 format when the sync starts. This option defaults to the current timestamp. |
Inherited Options
Name | Type | Required | Description |
|---|---|---|---|
-P, --profile | string | false | Name of the profile to use from your configuration file. To learn about profiles for MongoCLI, see https://dochub.mongodb.org/core/atlas-cli-configuration-file. |