[SERVER-16264] Allow unsharding a collection when all chunks are on the primary shard Created: 21/Nov/14 Updated: 06/Dec/22 Resolved: 05/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vincent | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 14 |
| Labels: | lamont-triage, pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Changing the shard key "on the fly" is pretty much impossible (see https://jira.mongodb.org/browse/SERVER-4000 ). While not ideal, this could work for some use cases. |
| Comments |
| Comment by Lamont Nelson [ 05/Nov/21 ] | ||||||||||||||||
|
Fixed with support for resharding. | ||||||||||||||||
| Comment by Nikolai Zujev [ 05/Jun/15 ] | ||||||||||||||||
|
+1 | ||||||||||||||||
| Comment by Anne Moroney [ 21/Nov/14 ] | ||||||||||||||||
|
+1 | ||||||||||||||||
| Comment by Vincent [ 21/Nov/14 ] | ||||||||||||||||
|
Absolutely, but with a command to properly unshard, instead of the dirt metadata removal requiring "shutdown all shards and all but one mongos which you are going to use to edit the metadata". Something like:
| ||||||||||||||||
| Comment by Roman Skvazh [ 21/Nov/14 ] | ||||||||||||||||
|
Did you mean https://jira.mongodb.org/browse/SERVER-9845 ? |