-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: 6.0.2
-
Component/s: None
-
Sharding EMEA
-
ALL
-
-
Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15
-
(copied to CRM)
As of v6.0.2 the getShardDistribution() is not able to recognize a sharded timeseries collection:
[direct: mongos] test> db.weather.getShardDistribution() MongoshInvalidInputError: [SHAPI-10001] Collection weather is not sharded
If invoked against the buckets collection, this will show some details, but a number of fields yield NaN:
[direct: mongos] test> db.system.buckets.weather.getShardDistribution() Shard shard01 at shard01/localhost:27018 { data: '718B', docs: undefined, chunks: 1, 'estimated data per chunk': '718B', 'estimated docs per chunk': NaN } --- Totals { data: '718B', docs: NaN, chunks: 1, 'Shard shard01': [ '100 % data', 'NaN % docs in cluster', '0B avg obj size on shard' ] }
This appears to be an oversight as the expectation is that getShardDistribution() should be able to recognize a sharded timeseries collection.
- depends on
-
MONGOSH-1447 getShardDistribution does not support sharded time series collections
- Closed
-
SERVER-76976 Programmatic API to get information on sharded collections
- Backlog