Deploy Three Config Servers for Production Deployments¶
This procedure converts a test deployment with only one config server to a production deployment with three config servers.
Use CNAMEs to identify your config servers to the cluster so that you can rename and renumber your config servers without downtime.
For redundancy, all production sharded clusters should deploy three config servers on three different machines. Use a single config server only for testing deployments, never for production deployments. When you shift to production, upgrade immediately to three config servers.
To convert a test deployment with one config server to a production deployment with three config servers:
Shut down all existing MongoDB processes in the cluster. This includes:
Copy the entire
dbPathfile system tree from the existing config server to the two machines that will provide the additional config servers. These commands, issued on the system with the existing Config Database,
mongo-config0.example.netmay resemble the following:
rsync -az /data/configdb mongo-config1.example.net:/data/configdb rsync -az /data/configdb mongo-config2.example.net:/data/configdb
Start all three config servers, using the same invocation that you used for the single config server.