MongoDB Upgrade from 2.4 to New Version ( 3.2)
Sanjay Gupta
Upgrade the cluster’s meta data
Pooja Gupta
Hi Sanjay,
- Should all cluster should be upgraded to 2.4 to 2.6 first and then follow same process from 2.6 to 3.0 and 3.0 to 3.2 ?
Yes, it is always recommended to complete the upgrade process to one version before moving onto the next.
It even did not mention that I need to shutdown existing config DB process. Do I need to shutdown 1 config server on shard and follow upgrade process ? Do I need to upgrade all config servers like this or since Config Server data is synched automatically , I need to upgrade only one config server and then replace binary for 2.6 on other servers.
For MongoDB versions 2.4, 2.6, 3.0 config servers are special mongod instances and not replica sets. Hence they have to be upgraded one by one as standalone mongod (shut down, upgrade and restart). Once you have upgraded your deployment to version 3.2, you can convert your mirrored config servers to Replica sets. But you have to make sure all the sharded cluster binaries must be at least version 3.2.4 before proceeding.
When doing upgrades, it is important that you follow our recommended best practices for the particular upgrade that you are undertaking. Please note that the recommended order regarding which instances to upgrade first varies from one upgrade to another. For example, to upgrade from 2.6.x to 3.0.x, one should do all mongos first, followed by all config server, and finally all mongod. This order is different than the order recommended for upgrading from 3.0.x to 3.2.x.
In addition, below are the links for your reference:
Regards,
Pooja