The tickets SERVER-13737 and SERVER-13927 both are a result of bad collection options.
The issue is that the collection options in "<db>.system.namespaces" can have fields in it that are invalid but not checked in 2.4. Since 2.6 has stricter validation, this causes problems with upgrading (manifested in the two tickets above).
Also need to add startup warning with remediation steps for this scenario.
See SERVER-6947 for an example of how these bad options can get in.
- is related to
-
SERVER-6947 db.createCollection creates undefined fields which cause mongorestore to fail
- Closed
-
SERVER-13737 CollectionOptions parser should skip "size"/"max" elements if values non-numeric
- Closed
-
SERVER-13927 Copydb breaks on (some) capped collections
- Closed
-
SERVER-13976 Cloner needs to detect failure to create collection
- Closed