Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
Description
Added a new field to server status
shardingStatistics.numShardedCollections that will be only present in the config server output and will represent total number of sharded collection in the cluster.
Description of Linked Ticket
We have made a lot of changes to the balancer. As a result, clusters with a high number of sharded collections may see slower balancing. In trying to find how many clusters have a high number of sharded collections, we realize that serverStatus doesn't give us this information.
We should track the number of sharded collections in a cluster and place that information in serverStatus. It would help to backport this to all the versions.
something like "numShardedCollections" or "catalogStatus.shardedCollections" may suffice.
This can be a lazy/slow count, aka can we do this in a way that doesn't impact customer workloads?
Attachments
Issue Links
- documents
-
SERVER-68576 We need to know how many sharded collections exist in a cluster
-
- Closed
-
- is depended on by
-
DOCS-15764 [SERVER][BACKPORT] [v5.0] We need to know how many sharded collections exist in a cluster
-
- Backlog
-
-
DOCS-15765 [SERVER] [v6.0] We need to know how many sharded collections exist in a cluster
-
- Backlog
-
-
DOCS-15766 [SERVER] [BACKPORT] [v4.4] We need to know how many sharded collections exist in a cluster
-
- Backlog
-
-
DOCS-15763 [SERVER][BACKPORT] [v6.2] We need to know how many sharded collections exist in a cluster
-
- Closed
-
- related to
-
DOCS-15763 [SERVER][BACKPORT] [v6.2] We need to know how many sharded collections exist in a cluster
-
- Closed
-