[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: |
|
||||||||||||||||||||
| 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... 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 |