[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:
Related
is related to SERVER-80488 Avoid traversing routing table in bal... Closed
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. 


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