[DOCS-15745] Investigate changes in SERVER-68576: We need to know how many sharded collections exist in a cluster Created: 17/Nov/22  Updated: 13/Nov/23  Resolved: 23/Jan/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 6.0.4, 6.3.0-rc0, 5.0.15, 6.2.0-rc2, 4.4.19, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ian Fogelman
Resolution: Fixed Votes: 0
Labels: ready-for-work
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DOCS-15764 [SERVER][BACKPORT] [v5.0] We need to ... Backlog
is depended on by DOCS-15765 [SERVER] [v6.0] We need to know how m... Backlog
is depended on by DOCS-15766 [SERVER] [BACKPORT] [v4.4] We need to... Backlog
is depended on by DOCS-15763 [SERVER][BACKPORT] [v6.2] We need to ... Closed
Documented
documents SERVER-68576 We need to know how many sharded coll... Closed
Related
related to DOCS-15763 [SERVER][BACKPORT] [v6.2] We need to ... Closed
Participants:
Days since reply: 1 year, 2 weeks, 2 days ago
Epic Link: DOCSP-22091

 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?



 Comments   
Comment by Githook User [ 23/Jan/23 ]

Author:

{'name': 'ianf-mongodb', 'email': '85948430+ianf-mongodb@users.noreply.github.com', 'username': 'ianf-mongodb'}

Message: DOCS-15745 v6.2 (#2422)

  • DOCS-15745 Adding numShardedCollections to serverStatus
  • code block
  • brackets
Comment by Garaudy Etienne [ 04/Jan/23 ]

Please make matt.panton@mongodb.com the external reviewer, please

Comment by Education Bot [ 29/Nov/22 ]

Fix Version updated for upstream SERVER-68576:
6.3.0-rc0, 6.0.4, 4.4.19, 6.2.0-rc2, 5.0.15

Comment by Education Bot [ 29/Nov/22 ]

Fix Version updated for upstream SERVER-68576:
6.3.0-rc0, 6.0.4, 6.2.0-rc2, 5.0.15

Comment by Education Bot [ 29/Nov/22 ]

Fix Version updated for upstream SERVER-68576:
6.3.0-rc0, 6.2.0-rc2, 5.0.15

Comment by Education Bot [ 29/Nov/22 ]

Fix Version updated for upstream SERVER-68576:
6.3.0-rc0, 5.0.15

Comment by Education Bot [ 24/Nov/22 ]

Fix Version updated for upstream SERVER-68576:
6.3.0-rc0

Comment by Garaudy Etienne [ 17/Nov/22 ]

right now, it's in code review for the master branch. we will backport it and link the releases once it's done. Assume 5.0 and newer.

Generated at Thu Feb 08 08:13:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.