From 7ffd15d28b860443fd7a89fdf6041920a415ddc0 Mon Sep 17 00:00:00 2001 From: Kevin Pulo Date: Fri, 5 Feb 2016 11:03:55 +1100 Subject: [PATCH] Do not recommend logical config server DNS names for CSRS The idea of having logical DNS names for the config servers only applies the old-style triplet of config servers. The rationale for it is being able to redirect the logical DNS name mapping to another host, in order to "swap out" one of the 3 config servers. However, in the context of config servers *as replsets*, this is bad advice - any situation where you would "swap out" an old-style config server, with CSRS you should instead just use normal replica set management operations to handle (eg. add a new member, remove another member, etc). --- source/tutorial/deploy-shard-cluster.txt | 2 -- 1 file changed, 2 deletions(-) diff --git a/source/tutorial/deploy-shard-cluster.txt b/source/tutorial/deploy-shard-cluster.txt index cd186de1ff2..ebe8ea2bb8e 100644 --- a/source/tutorial/deploy-shard-cluster.txt +++ b/source/tutorial/deploy-shard-cluster.txt @@ -50,8 +50,6 @@ Deploy the Config Server Replica Set The config servers store the sharded cluster's metadata. The following steps deploy a three member replica set for the config servers. -.. include:: /includes/tip-hostnames.rst - #. Start all the config servers with both the :option:`--configsvr` and :option:`--replSet \ <--replSet>` options: