Currently, the schema upgrade work is done in SetFeatureCompatibilityVersionCmd::run(), which is not run when config servers run _configsvrSetFeatureCompatibilityVersion upgrade, and so collections in config do not get assigned UUIDs.
This ticket should make setFeatureCompatibilityVersion take a ResourceMutex so that only one instance of it can run at a time.
It should also prevent a user from initiating downgrade while a previous upgrade has not completed and vice versa.
- is depended on by
-
SERVER-31231 prevent addShard and shardCollection from running concurrently with setFCV
- Closed
- is duplicated by
-
SERVER-31214 config server should call setFeatureCompatibilityVersion on itself as part of _configsvrSetFeatureCompatibilityVersion
- Closed
- related to
-
SERVER-31017 Race condition in setFeatureCompatibilityVersion command leads to fCV=3.6 and isSchemaVersion36=false
- Closed
-
SERVER-32284 awaitReplication can hang when the optime to wait for does not match the minSnapshot.
- Closed