[SERVER-75472] Support transition from standalone replica set directly to catalog shard Created: 30/Mar/23 Updated: 27/Oct/23 Resolved: 14/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Sprint: | Sharding NYC 2023-05-15 | ||||||||
| Participants: | |||||||||
| Description |
|
To convert a standalone replica set to a sharded cluster, we currently require users start a fresh config server, restart every replica set node with the --shardsvr command line option, then add the shard to the cluster. If a user wants to convert to a one shard cluster with a colocated config server shard (ie a catalog shard), they should be able to restart the standalone set's nodes with the --configsvr command line option, which is currently not allowed. |
| Comments |
| Comment by Randolph Tan [ 14/Aug/23 ] |
|
PM-2966 makes this obsolete |
| Comment by Jack Mulrow [ 30/Mar/23 ] |
|
We won't do this as part of PM-2290, marking as related to PM-2290 and moving it out of the project and pushing out a few sprints. |
| Comment by Garaudy Etienne [ 30/Mar/23 ] |