[SERVER-71118] Changes to sh.status() for 6.0.3+ clusters Created: 07/Nov/22 Updated: 24/Nov/22 Resolved: 23/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Martin Barciela Pires | Assignee: | Anna Henningsen |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding EMEA 2022-12-12 | ||||||||
| Participants: | |||||||||
| Description |
|
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:
Or something similar to the $shardedDataDistribution aggregation stage.
|
| Comments |
| Comment by Tommaso Tocci [ 23/Nov/22 ] |
|
max.hirschhorn@mongodb.com I've got a confirmation from anna.henningsen@mongodb.com that since version 6.0.0 the legacy shell isn't being published anymore, and is only for the server team's internal use for testing. Thus I'm going to close this ticket, we will instead address this in MONGOSH-1326. |
| Comment by Tommaso Tocci [ 23/Nov/22 ] |
|
Created MONGOSH-1326 to also address this in the new mongosh shell. |
| Comment by Max Hirschhorn [ 07/Nov/22 ] |
|
The legacy mongo shell is no longer released with the server binaries in MongoDB 6.0. Should this change be targeted for the new mongosh shell? |