Include the ability to do an upgrade check for users coming from versions prior to 2.6.
Invoke from a 2.6 mongo shell connected to a <2.6 mongod or mongos.
There is the option to only run the checks on an individual db or collection, as well as the ability to skip document level checks.
The shell helper checks the following data and index issues that are no longer valid in 2.6:
- collections without _id field (only possible <= 2.0)
- documents with index keys that are greater than max size (max size depends on key type and index version)
- invalid index specs
- documents with illegal field names
- is related to
-
SERVER-12841 upgradeCheck() gives unhelpful message for _id too long to index
- Closed
-
SERVER-15731 Pre-flight upgrade tool to check for changes breaking backwards compatibility or introducing regressions in 2.8
- Closed
-
SERVER-12070 Validate all indexes for new restrictions at startup
- Closed
-
SERVER-5290 fail to insert docs with fields too long to index, and fail to create indexes where doc keys are too big
- Closed
-
SERVER-12233 Command to check for over-long index keys
- Closed
- related to
-
SERVER-12828 Reindexing drops indexes if key contains values too large to index
- Closed
-
SERVER-13129 db.upgradeCheck() no longer checks all collections by default, and ignores db parameter
- Closed
-
SERVER-13130 db.upgradeCheck() or db.upgradeCheckAllDbs() can time out
- Closed
-
SERVER-12806 Object.invalidForStorage error messages reference 'okForStorage' method
- Closed
-
SERVER-9516 Upgrade/downgrade support for new schema for user and role data
- Closed
-
SERVER-12836 upgradeCheck() or collUpgradeCheck() should exclude changelog collection
- Closed
-
SERVER-12837 upgradeCheck() prints way too much output in default mode
- Closed
-
SERVER-12838 invalidForStorage should return actual error
- Closed
-
SERVER-13003 upgradeCheck on admin db should check all db's
- Closed