Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-71118

Changes to sh.status() for 6.0.3+ clusters

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA 2022-12-12

      Starting in 6.0.3, where a shared cluster would be balancing the shards using range migration based on the volume of data in the namespace, the current output of the sh.status() does not help to identify if the cluster is well balanced. 

      Considering the balancing of a sharded namespace would be sensitive to orphans and data volume, and in order to count with a mechanism that easily allows checking the current state of the cluster, it would be good if the sh.status() provides the following information per sharded namespaces:

      • Estimated number of orphan documents per shard
      • Data volume per shard

      Or something similar to the $shardedDataDistribution aggregation stage.

       

            Assignee:
            anna.henningsen@mongodb.com Anna Henningsen
            Reporter:
            martin.barciela-pires@mongodb.com Martin Barciela Pires
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: