-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
Storage 2017-08-21, Storage 2017-09-11, Storage 2017-10-23
There are some non-trivial code paths (e.g: shutdown) that can happen before FCV is initialized (inside `repairDatabasesAndCheckVersion`). These non-trivial code paths may require reading FCV from memory and may incorrectly read the default 3.4 as opposed to an explicitly set 3.4.
The example of WiredTiger shutdown that wants to know the FCV value can make a sane decision with an uninitialized value. It's presumed this state would be sufficient for future cases.
- depends on
-
SERVER-31235 Fix or blacklist jstests/multiVersion/3_upgrade_replset.js to not rely on unintentional WiredTiger downgrade
- Closed
- has to be done before
-
SERVER-31137 Assert that the featureCompatibilityVersion server parameter is initialized from the featureCompatibilityVersion document during startup
- Closed
- is depended on by
-
SERVER-31136 Add method to determine whether fCV has been set
- Closed
-
SERVER-31211 Use config_base=false for encryption at rest WT instance.
- Closed