Details
-
Bug
-
Resolution: Works as Designed
-
Major - P3
-
None
-
None
-
None
-
*Location*: https://docs.mongodb.com/v3.2/tutorial/upgrade-config-servers-to-replica-set/
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.40 Safari/537.36
*Referrer*: https://docs.mongodb.com/manual/release-notes/3.2-upgrade/
*Screen Resolution*: 1920 x 1080
*Location*: https://docs.mongodb.com/v3.2/tutorial/upgrade-config-servers-to-replica-set/ *User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.40 Safari/537.36 *Referrer*: https://docs.mongodb.com/manual/release-notes/3.2-upgrade/ *Screen Resolution*: 1920 x 1080
Description
First paragraph says: To deploy config servers as a replica set, the config servers must run the WiredTiger storage engine.
Then in step 4: If the config server is using MMAPv1, start 3 new mongod instances.
OR
The example in this procedure assumes that the existing config servers use MMAPv1.
WTF?