-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: 8.0.4
-
Component/s: None
-
Cluster Scalability
Today when a customer unshards a collection that has a zone definition the unshard command fails.
MongoServerError: Specified zones and shardDistribution are conflicting with the existing shard/zone, shard configdoesn't belong to zone zone_two
It would be better if the system automatically removed the zone configuration for the collection as unsharded collections cannot have zone configurations and saves the customer time of manually removing the zone information.
This change should come with a docs update that states unsharding a collection will remove any zone configuration for the namespace if configured.