Details
-
Bug
-
Resolution: Won't Do
-
Major - P3
-
None
-
*Location*: https://docs.mongodb.org/manual/tutorial/upgrade-config-servers-to-replica-set/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/release-notes/3.2-upgrade/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: tutorial/upgrade-config-servers-to-replica-set
*Location*: https://docs.mongodb.org/manual/tutorial/upgrade-config-servers-to-replica-set/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/release-notes/3.2-upgrade/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: tutorial/upgrade-config-servers-to-replica-set
Description
I think this doc has something wrong.
In point 7 you shut down one of the remaining (second or third) config server, and it becomes read only.
Then in point 11, we restart the first config server and you say it is now writeable, but the config server that was shut down in point 7 is still down, so we are still in a 2 nodes config server, it shouldn't be writeable. Or maybe 1 node, because the first server is in state REMOVED within his replicaset.
The thing is that i don't see the goal of point 7, why do you need to take the second or the third config server down?