Upgrading MongoDB to 2.6
Prepare for upgrade
1. Connect the 2.6 MONGO shell to the 2.4 replica set secondary member and execute Db.upgradecheckalldbs () in the admin library.
2. Evaluate application compatibility issues for upgrade to 2.6, refer to: http://docs.mongodb.org/manual/release-notes/2.6-compatibility/
Single Instance Upgrade
1. Close the Mongod instance, replace it with the 2.6 mongod binary, and restart the instance.
Replica set Upgrade
1. Upgrade replica set secondary members.
Upgrade each secondary member in turn.
Restart the instance by shutting down the Mongod instance, replacing the 2.4 binary with the 2.6 mongod binary file.
After the Member State is checked by Rs.status (), wait for the instance state to revert to the secondary state, and then upgrade the next secondary member.
2. Demote the replica set Master member.
Use Rs.stepdown () to force a failover of the primary library.
3. Upgrade the Master member.
Confirm that the Rs.status () Main library status is degraded and that a member is promoted to the primary member.
Close the original member instance, replace it with the 2.6 mongod binary, and restart the instance.
Reference:
http://docs.mongodb.org/manual/release-notes/2.6-upgrade/
http://docs.mongodb.org/manual/reference/method/db.upgradeCheckAllDBs/#db. Upgradecheckalldbs
http://docs.mongodb.org/manual/release-notes/2.6-compatibility/
This article is from the SQL Server deep dives blog, so be sure to keep this source http://ultrasql.blog.51cto.com/9591438/1658359
Upgrade MongoDB to 2.6