-
Type: Task
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
2
-
Not Needed
Running db.collection.getShardDistribution() directly on a shard primary reports Collection X.Y is not sharded. even though it is. Running via a mongos correctly reports shard information.
I think when running directly on a node, Mongo shell should instead respond "This command should be run via a mongos" or "Please connect to a mongos before calling this function"
- is related to
-
COMPASS-6872 Investigate changes in PM-3364: Track unsharded collections in the sharding catalog upon moveCollection
- Closed