-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
None
-
Fully Compatible
-
Storage 2018-02-12, Storage 2018-02-26
In 3.6, a missing featureCompatibilityVersion document could be restored by running the database with --repair (see SERVER-29452). In 4.0, the document should be similarly restored, except --repair should fail unless all collections have UUIDs and otherwise restore the featureCompatibilityVersion document with "version" equal to 3.6. The set_feature_compatibility_version.js test contains testing for using --repair to restore the featureCompatibilityVersion document. This testing should be updated to reflect the new semantics and new fCV values.
- has to be done after
-
SERVER-32741 Bump the default value of the featureCompatibilityVersion parameter to 3.6
- Closed
- is duplicated by
-
SERVER-32838 Refuse to restore the featureCompatibilityVersion document unless all collections have UUIDs
- Closed
- is related to
-
SERVER-29452 Handle missing featureCompatibilityVersion document during startup
- Closed
-
SERVER-32807 Move the FCV on mongod start-up testing out of multiVersion/set_feature_compatibility_version.js and into a new separate JS file
- Closed