[SERVER-38627] removeShard support for unsharded collections Created: 13/Dec/18 Updated: 27/Oct/23 Resolved: 15/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | pm-1051-legacy-tickets, sharding-common-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
Hence the removeShard needs to drain the shard being removed first and unsharded collections chunks can be moved there the command needs to migrate the unsharded collections either back to primary or distribute (most likely the latter) |
| Comments |
| Comment by Sergi Mateo Bellido [ 15/Nov/22 ] |
|
The current behavior will be that the removeShard will inform you that you have to run movePrimary first in order to be able to remove that shard. |