-
Type:
Improvement
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.4.8, 2.6.3
-
Component/s: Sharding
-
None
-
Sharding
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Right now mongoS doesn't automatically refresh the config metadata prior to sharding a collection. It might cause certain operational inconvenience e.g. if you have multiple mongoS instances and you drop the collection on one of them - you won't be able to re-shard it on any other mongoS.