[SERVER-9265] split command should take options: maxChunkSize, numChunks, complete Created: 05/Apr/13 Updated: 06/Dec/22 Resolved: 26/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | commands, investigation, mongos, split | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Participants: | |||||
| Story Points: | 3 | ||||
| Description |
|
These options will allow finer grain control over the split process. maxChunksSize: [opt] Used to define resulting chunk sizes |
| Comments |
| Comment by Pierlauro Sciarelli [ 26/Apr/22 ] |
|
Closing as "won't do" given that after the NOMAS project:
|
| Comment by Kaloian Manassiev [ 12/Feb/22 ] |
|
Actually I was wrong, there will still be split command, but it is not expected to be used by anyone because the shard will be maintaining its internal statistics to help the balancer make decisions. Because of this, there will never be a reason for customers to call split. I am putting this ticket under the NoMAS project. |
| Comment by Lamont Nelson [ 11/Feb/22 ] |
|
kaloian.manassiev What will the split command be replaced with? |
| Comment by Lamont Nelson [ 11/Feb/22 ] |
|
I'm not sure that it is related to HELP-31183. Or at least I don't have any evidence at the moment to say that it is. andrew.shuvalov did you add this link? |