[SERVER-55430] Record metrics about whether a collection is rebalanced after resharding op finishes Created: 22/Mar/21 Updated: 29/Oct/23 Resolved: 23/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc3, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Randolph Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||||||||||
| Sprint: | Sharding 2021-06-14, Sharding 2021-06-28 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||
| Description |
|
Resharding attempts to create an initial chunk distribution such that the collection will not be rebalanced by the balancer immediately after (absent of any topology changes, etc of course). It would be useful to collect metrics on whether the balancer rebalances a collection that has just been resharded in order to determine whether resharding's initial split policy is in fact creating a good initial distribution. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 16/Jun/21 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}Message: (cherry picked from commit 5c00024e3cf4a27039117e000e475c6ee797c700) |
| Comment by Githook User [ 16/Jun/21 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}Message: |
| Comment by Janna Golden [ 03/Jun/21 ] |
|
Hmm, renctan that's a good point about it being difficult to know what collections have been resharded recently. I think max.hirschhorn's idea about recording it in the ReshardingMetrics makes sense, we'd essentially just want to check that the initial split alg is putting this "ideal number of chunks per shard. I think it might even make sense to do it when we create the chunks because we have access to the shard info (what zones are associated with what shards) there as well, though I don't know if we have access to the ReshardingMetrics at that point. |
| Comment by Max Hirschhorn [ 02/Jun/21 ] |
|
renctan, I think a per-collection metric could make it difficult to get reporting on because per-collection metrics aren't something we could add to a serverStatus section tracked by FTDC since would lead to excessive schema changes (e.g. as what happened with the range deleter and |
| Comment by Randolph Tan [ 02/Jun/21 ] |
|
max.hirschhorn, janna.golden. Here are my proposal for this ticket, what do you guys think?
|