[SERVER-74584] Splitting chunks for zone violations must not impact scalability Created: 03/Mar/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | balancer-round-perf, oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Within the balancer round we are travearsing all the chunks per collection to check if any chunk needs to be split due to zone violations. The aim of this ticket is to reduce the amount of time this check takes in case of having a large number of collections. A proposal is to modify the selectChunksToSplit implementation and perform a query joining config.tags and config.chunks to find the chunks violating zones instead of bringing to memory all the zones and all the collection distributions. |