[SERVER-68576] We need to know how many sharded collections exist in a cluster Created: 04/Aug/22  Updated: 29/Oct/23  Resolved: 24/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.19, 5.0.15, 6.0.4, 6.2.0-rc2, 6.3.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Garaudy Etienne Assignee: Pol Pinol
Resolution: Fixed Votes: 1
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-15745 Investigate changes in SERVER-68576: ... Closed
Problem/Incident
causes SERVER-74720 The default 'shardingStatistics' serv... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.2, v6.1, v6.0, v5.0, v4.4
Sprint: Sharding EMEA 2022-11-28
Participants:
Story Points: 3

 Description   

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 [ 29/Nov/22 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-68576 Added number of sharded collections to serverStatus command.
Branch: v4.4
https://github.com/mongodb/mongo/commit/6e3beb9b537815b1d6efa4cb530037c99261d10a

Comment by Githook User [ 29/Nov/22 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-68576 Added number of sharded collections to serverStatus command.
Branch: v6.0
https://github.com/mongodb/mongo/commit/48476ee2af534a9efdd238f753ac7e271ec660dd

Comment by Githook User [ 29/Nov/22 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-68576 Added number of sharded collections to serverStatus command.
Branch: v5.0
https://github.com/mongodb/mongo/commit/e6459ee3049b2bfa1010142394e9d0df290b68ec

Comment by Githook User [ 29/Nov/22 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-68576 Added number of sharded collections to serverStatus command.
Branch: v6.2
https://github.com/mongodb/mongo/commit/923b5fd65ad075c7da30af55022df936f4339128

Comment by Githook User [ 24/Nov/22 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-68576 Added number of sharded collections to serverStatus command.
Branch: master
https://github.com/mongodb/mongo/commit/01a33462d48fc4b44f9d4e7eeff632995a7f9ceb

Comment by Pol Castuera (Inactive) [ 23/Aug/22 ]

Not yet. tommaso.tocci@mongodb.com is reviewing the PR and he will give more context about next steps. 

Comment by Garaudy Etienne [ 22/Aug/22 ]

do I need to request a backport?

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