[SERVER-82760] Report number of sharded/unsharded collections in server status Created: 03/Nov/23 Updated: 04/Nov/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
The numShardedCollections metric reported in configsvr's server status output is currently based on the number of records present in config.collections. Once unsharded collections are also going to be also tracked in the same collection, a simple count will not be enough to differentiate between sharded and unsharded collections. Purpose of this ticket is to start reporting 2 separate metrics (numShardedCollections and numUnshardedCollections) by replacing the count with a query taking into account the unsplittable field. |