Description

Hi!

I have a replica set of three nodes, and I want rename it.

The documentation https://docs.mongodb.com/manual/tutorial/rename-unsharded-replica-set/ says that in order to rename a replica set I have to:

1. make a backup,
2. stop all nodes of the replica set,
3. change the name of the replica set to mongod.conf (I'm using a configuration file),
4. enable them without a replica set,
5. change the name of the replica set in the locale database,
6. enable all nodes again as a replica set.

The backup is needed as insurance against incorrect actions when renaming a replica set.
Then I can do this:

1. Change the replica set name in the configuration file,
2. Change the replica set name in the locale base on each node sequentially,
3. Turn off successively the secondary nodes,
4. Restart the primary node,
5. Turn on the secondaries of the node in sequence.

During times 1 and 2, the set is available for writing and reading. At time 3, it is read-only. i tested this on 4.2+ versions with C# driver.

This way, I minimize the time the replica set is unavailable until the restart time of the two nodes.

Why is my varinat dangerous? What problems can arise if you do this?

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)