-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Catalog and Routing
-
ALL
-
Sharding 2020-10-19, Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11
-
0
During addShard we find any databases that already exist on the shard being added and attempt to add them to the cluster. If this fails for any reason, however, we log a message and continue. This feels like a bad idea as now a) databases that a user might have been expecting to be visible to the cluster are now hidden and b) while I have not verified this, I suspect this could cause problems if a database with the same name is created sometime in the future.