Migrate Config Servers with the Same Hostname¶
This procedure applies to migrating config servers when using three
mongod instances as config servers.
For replacing config servers deployed as members of a replica set, see Replace a Config Server.
To migrate all three mirrored config servers, perform this procedure for
each config server separately and migrate the config servers in reverse
order from how they are listed in the
configDB string. Start with the last config server
listed in the
Shut down the config server.
This renders all config data for the sharded cluster “read only.”
Change the DNS entry that points to the system that provided the old config server, so that the same hostname points to the new system. How you do this depends on how you organize your DNS and hostname resolution services.
Copy the contents of
dbPathfrom the old config server to the new config server.
For example, to copy the contents of
dbPathto a machine named
mongodb.config2.example.net, you might issue a command similar to the following:
rsync -az /data/configdb/ mongodb.config2.example.net:/data/configdb
Start the config server instance on the new system. The default invocation is:
When you start the third config server, your cluster will become writable and it will be able to create new splits and migrate chunks as needed.