[DOCS-4798] Add docs for changing replica set name Created: 09/Feb/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Peter Garafano (Inactive) Assignee: Susan Kerschbaumer (Inactive)
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates DOCS-2056 Document how to rename a replica set Closed
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 1.5

 Description   
  1. Stop all the servers
  2. Start up each server without the --replSet option, pointing at the correct data directory. If the replica set is a shard or config server, you must start the server without --shardsvr and --configsvr respectively. If we backport this to 3.2, we user must instead include --setParameter=recoverShardingState=false and exclude --configSvrmode
  3. Update the local.system.replset doc on each server with the new replica set name. You have to change every server here.
  4. Shut them down again.
  5. Change the /etc/mongod.conf replSet option to the new name on all the servers.
  6. Start them all up with the original options.


 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Eric Milkie [ 07/Nov/16 ]

Yes, the procedures should work for all versions of MongoDB.
The only part you might need to change is step 5, which needs to be made more generic and not assume that everyone is using a configuration file and that it is stored in /etc.

Comment by Ravind Kumar (Inactive) [ 07/Nov/16 ]

milkie,siyuan.zhou I just want to confirm these procedures would work for most / all versions of MongoDB.

Thanks!

Generated at Thu Feb 08 07:48:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.