On this page
New in version 3.4.
Removes the association between a zone and a shard.
sh.removeShardFromZone()when connected to a
sh.removeShardFromZone() does not remove ranges associated with the
To completely remove a zone from the cluster, you must run
sh.removeShardFromZone() on each shard associated with the zone.
If the shard specified is the last shard associated with the zone, you
must ensure there are no remaining ranges associated with the zone. Use
updateZoneKeyRange to remove any existing ranges associated to
the zone before running
See the zone manual page for more information on zones in sharded clusters.
Removing the association between a zone and a shard removes the constraints keeping chunks covered by the zone on the shard. During the next balancer round, the balancer may migrate chunks that previously covered by the zone.
See the sharded cluster balancer manual page for more information on how migrations work in a sharded cluster.
For sharded clusters that enforce access control, you must authenticate either as:
a user whose privileges include:
shardscollection in the
tagscollection in the
a user whose privileges include
enableShardingon the cluster resource (available starting in version 4.2.2, 4.0.14, 3.6.16).
clusterManager built-in roles have
the appropriate permissions for issuing
See the Role-Based Access Control manual page for more
The following example removes the association between
shard0000 and the