[SERVER-3566] Support draining if maxSize added or changed Created: 10/Aug/11 Updated: 06/Dec/22 Resolved: 06/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Y. Wayne Huang | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | sharding, tommaso-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
currently, if maxSize is added or changed on a shard that already has more data than maxSize, it doesn't seem as if the balancer will migrate chunks off of the shard. this could be useful in situations where the underlying hardware has changed (less ram, less disk, or both). |
| Comments |
| Comment by Pierlauro Sciarelli [ 06/May/22 ] |
|
Closing as "Won't do" because of |
| Comment by Kaloian Manassiev [ 06/Nov/21 ] |
|
tommaso.tocci, I believe this might belong under the AutoSplitter project's subsequent milestones (if we will be doing something smarter around tracking deletes). |
| Comment by MediaMath Mongo [ 24/May/12 ] |
|
|