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

    XMLWordPrintableJSON

Details

    • Hide
      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.
      Show
      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

      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?

      Attachments

        Issue Links

          documents

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-68576 We need to know how many sharded collections exist in a cluster

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Task - A task that needs to be done. DOCS-15764 [SERVER][BACKPORT] [v5.0] We need to know how many sharded collections exist in a cluster

          • Major - P3 - Major loss of function.
          • Backlog

          Task - A task that needs to be done. DOCS-15765 [SERVER] [v6.0] We need to know how many sharded collections exist in a cluster

          • Major - P3 - Major loss of function.
          • Backlog

          Task - A task that needs to be done. DOCS-15766 [SERVER] [BACKPORT] [v4.4] We need to know how many sharded collections exist in a cluster

          • Major - P3 - Major loss of function.
          • Backlog

          Task - A task that needs to be done. DOCS-15763 [SERVER][BACKPORT] [v6.2] We need to know how many sharded collections exist in a cluster

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. DOCS-15763 [SERVER][BACKPORT] [v6.2] We need to know how many sharded collections exist in a cluster

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:
                35 weeks, 6 days ago