[SERVER-2472] ability to split and balance chunks based on load and not only based on chunk size Created: 03/Feb/11  Updated: 16/Jan/24

Status: Blocked
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Oded Maimon Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 4
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-9477 New migration policy for selecting ch... Closed
Related
is related to SERVER-9114 Add balancer strategy that balances b... Blocked
Assigned Teams:
Cluster Scalability
Participants:

 Description   

currently mongodb will rebalance chunks on inserts, but in some cases the collection key is a numeric sequence which makes all first X amount of records go to one server and the second to the other...
this is ok as long as the load on that collection is not high, but if the collection usage is high, it means that manual sharding should be invoked by the admin.

i think that re-balancing a collection based on its load should also be added to the balancer. when a collection chink have a high load of queries the chunk should be splited and move to the other server/servers...



 Comments   
Comment by Connie Chen [ 18/Jan/23 ]

Taking out of PM-631 and placing in "Needs Scheduling" since we have closed PM-631 as won't do 

Comment by Glenn Maynard [ 06/Apr/12 ]

The webpage says that MongoDB already splits based on load:

http://www.mongodb.org/display/DOCS/Sharding
> Automatic balancing for changes in load and data distribution

Generated at Thu Feb 08 03:00:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.