-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Upgrade/Downgrade
-
Fully Compatible
-
v3.6
-
Storage 2017-11-13, Storage 2017-12-04
-
0
Removing the featureCompatibilityVersion document, dropping the admin.system.version collection, or dropping the admin database should fail. This can either fail by fasserting or by aborting the transaction and returning an error. If we fail by fasserting, we should be able to recover using the startup parameter in SERVER-29452.
Mongod 3.6 must always have the featureCompatibilityVersion document, as described in SERVER-29452.
- depends on
-
SERVER-29452 Handle missing featureCompatibilityVersion document during startup
- Closed
- is related to
-
SERVER-29350 Bump featureCompatibilityVersion to 3.6
- Closed
-
SERVER-29448 Disallow dropping "admin" and "local" dbs when in replica set mode
- Closed
- related to
-
SERVER-32097 Updating the FCV document directly between 3.4/3.6 can crash secondaries.
- Closed
-
SERVER-35136 Remove featureCompatibilityVersion document restoration based on UUIDs during --repair
- Closed
-
SERVER-64491 Reconsider allowing the system.js collection to be renamed
- Closed