Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
*Location*: http://docs.mongodb.org/manual/release-notes/3.0-upgrade/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/release-notes/3.0/
*Screen Resolution*: 1366 x 768
*repo*: docs
*source*: release-notes/3.0-upgrade
*Location*: http://docs.mongodb.org/manual/release-notes/3.0-upgrade/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/release-notes/3.0/ *Screen Resolution*: 1366 x 768 *repo*: docs *source*: release-notes/3.0-upgrade
Description
We link to the 2.6 upgrade documentation in the last bullet of this section - http://docs.mongodb.org/manual/release-notes/3.0-upgrade/#upgrade-a-replica-set-to-3-0
So it seems like we're referring to the process users should follow if they're running a version prior to 2.6 but we don't say that.
We say this:
To upgrade a replica set from MongoDB 2.6 to 3.0, upgrade all members of the replica set to version 2.6 first, and then follow the procedure to upgrade from MongoDB 2.6 to 3.0.
It should say something like:
To upgrade a replica set to 3.0 from a MongoDB version prior to 2.6, upgrade all members of the replica set to version 2.6 first, and then follow the procedure to upgrade from MongoDB 2.6 to 3.0.