Start Dbs 6 updating ports tree

Dbs 6 updating ports tree

For example, during the upgrade, do not do any of the following: process.

and run the db.upgrade Check All DBs() to check your data set for compatibility. Assess and resolve all issues identified by db.upgrade Check All DBs().

Some changes in Mongo DB 2.6 require manual checks and intervention. Resolve all incompatibilities in your deployment before continuing.

This can reintroduce old meta-data formats into the config servers.

The meta-data change made by this upgrade process will help prevent errors caused by cross-version incompatibilities in future versions of Mongo DB.

Replica set failover is not instant and will render the set unavailable to accept writes until the failover process completes.

This may take 30 seconds or more: schedule the upgrade procedure during a scheduled maintenance window.

Therefore you cannot perform a rolling upgrade from Mongo DB 2.2.0 to Mongo DB 2.4.0.

To upgrade a cluster with 2.2.0 components, use one of the following procedures.

Before beginning the upgrade process for a deployment that uses authentication and authorization: , and then follow the procedure to upgrade from Mongo DB 2.4 to 2.6.

You can upgrade from Mongo DB 2.4 to 2.6 using a “rolling” upgrade to minimize downtime by upgrading the members individually while the other members are available: Replica set failover is not instant but will render the set unavailable accept writes until the failover process completes.

Earlier versions of Mongo DB do not correctly handle epochs.