Definition
Stops the in-progress transition from an embedded config server to a dedicated config server.
The shard resumes its role in the sharded cluster and is included in rebalancing operations.
When the command runs, the in-progress transition from an embedded config server to a dedicated config server stops by terminating the draining of chunks from the config shard. The config shard then resumes its normal role in balancing.
The command returns ok: 1 on success, otherwise it returns ok: 0 with a related error message.
To start transitioning to a dedicated config server, see the startTransitionToDedicatedConfigServer command.
To show the status of the transition from an embedded config server to a dedicated config server, see the getTransitionToDedicatedConfigServerStatus command.
To commit the transition from an embedded config server to a dedicated config server, see the commitTransitionToDedicatedConfigServer command.
New in version 8.3. :
Compatibility
This command is available in deployments hosted in the following environments:
MongoDB Enterprise: The subscription-based, self-managed version of MongoDB
MongoDB Community: The source-available, free-to-use, and self-managed version of MongoDB
Note
This command is not supported in MongoDB Atlas. Contact MongoDB support to stop the transition from an embedded to dedicated config server.
Syntax
The command has the following syntax:
db.adminCommand( { stopTransitionToDedicatedConfigServer: 1 } )
Behavior
Access Requirements
If you have authorization enabled, you must have the clusterManager role or any role that includes the removeShard action.
Examples
To start transitioning from an embedded to a dedicated config server, use the db.adminCommand() method to run the startTransitionToDedicatedConfigServer command:
db.adminCommand( { startTransitionToDedicatedConfigServer: 1 } )
To stop transitioning from an embedded to a dedicated config server, use the db.adminCommand() method to run the stopTransitionToDedicatedConfigServer command:
db.adminCommand( { stopTransitionToDedicatedConfigServer: 1 } )