[SERVER-46905] Test the commonly used procedure for renaming shards Created: 16/Mar/20 Updated: 06/Dec/22 Resolved: 26/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
Renaming replica sets is not supported by the server, but there is a commonly used procedure for doing so that involves shutting down the cluster. We should write a test for this procedure, so that we will be aware if we break it. |
| Comments |
| Comment by Garaudy Etienne [ 26/May/22 ] |
|
This test is not simple because it requires patching up all persisted documents that contain a shardId. If we decide to create an officially supported way of rename replica sets, then we may revisit/reopen this ticket. |
| Comment by Tommaso Tocci [ 26/Apr/22 ] |
|
CC garaudy.etienne@mongodb.com to define the priority of this work |