Sharding Commands
Note
For details on a specific command, including syntax and examples, click on the link to the command's reference page.
Name | Description |
---|---|
Aborts a resharding operation. New in version 5.0. | |
Adds a shard to a sharded cluster. | |
Returns information on whether the chunks of a sharded collection are balanced. | |
Starts a balancer thread. | |
Returns information on the balancer status. | |
Stops the balancer thread. | |
Clears the | |
Removes orphaned data with shard key values outside of the ranges of the chunks owned by a shard. | |
Cleans up a failed resharding operation. New in version 5.0. | |
Forces a resharding operation to block writes and complete. New in version 5.0. | |
Enables sharding on a specific database. | |
Returns the hostnames and connection strings for shards in the cluster and the config servers for your cluster. | |
Verifies that a process is a | |
Returns a list of configured shards. | |
Internal command that migrates chunks between shards. | |
Reassigns the primary shard when removing a shard from a sharded cluster. | |
Provides the ability to combine chunks on a single shard. | |
Refines a collection's shard key by adding a suffix to the existing key. | |
Starts the process of removing a shard from a sharded cluster. | |
Initiates a resharding operation to change the shard key for a collection, changing the distribution of your data. New in version 5.0. | |
Prevents the start of new automatic migrations on a collection, prevents in-flight manual migrations from committing, and excludes the collection from new balancer rounds. | |
Enables the sharding functionality for a collection, allowing the collection to be sharded. | |
Reports whether the | |
Creates a new chunk. | |
Removed in MongoDB 5.0. Internal command that affects connections between instances in a MongoDB deployment. | |