[SERVER-1037] Sharding - command to remove or "unshard" a collection Created: 21/Apr/10 Updated: 06/Dec/22 Resolved: 03/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Kyle Banker | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 13 |
| Labels: | sharding-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Still hasn't come up - so pushing for now unless there is a compelling reason to do sooner. |
| Comments |
| Comment by Kaloian Manassiev [ 03/May/18 ] |
|
Closing as duplicate of |
| Comment by Michael Ahlijah [ 27/Mar/18 ] |
|
So when is this getting resolved? This issue has been open for 8 years so is there a plan to get it fixed? |
| Comment by Eliot Horowitz (Inactive) [ 16/Jul/10 ] |
|
moved to 1.7 early |
| Comment by Alberto Lerner [ 16/Jul/10 ] |
|
@eliot It is similar in that, as in dropshard, the balancer's decisions is influenced by the command. I'd prefer, however, that we had a more generic mechanism of "shard groups". Distribution of chunks of a collection anchored to a shard group would be done on shards within the group. Nothing prevents a group to be made of one shard. @ kyle, eliot Although I can imagine use cases for this, I wonder if (a) you'd agree with the generalization above and (b) that we should wait for actual cases to appear so to determine the right behavior we want to have. If you think that's reasonable, I'd push this to 1.7 and present a candidate design doc for it then. |
| Comment by Eliot Horowitz (Inactive) [ 22/Jun/10 ] |
|
pretty similar to dropshard i think |