Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15745

Investigate changes in SERVER-68576: We need to know how many sharded collections exist in a cluster

      Original Downstream Change Summary

      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?

            Assignee:
            ian.fogelman@mongodb.com Ian Fogelman
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:
              1 year, 21 weeks, 5 days ago