-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-10-23, Repl 2017-11-13
-
0
SERVER-31019 will not fail initial sync if the upgrade/downgrade began before initial sync and finishes after. Having UUIDs get added while initial sync is occurring sounds potentially dangerous. Additionally, SERVER-29452 forces 3.6 binaries to fail to start up if there is no featureCompatibilityVersion document. They should therefore fail to initial sync from sources that do not have a featureCompatibilityVersion document.
- depends on
-
SERVER-31634 FeatureCompatibilityVersion::setIfCleanStartup() should store FCV=3.4 for shardsvrs
- Closed
- is depended on by
-
SERVER-29452 Handle missing featureCompatibilityVersion document during startup
- Closed
- is duplicated by
-
SERVER-86142 Handle FCV change during initial sync while copying collections with recordIdsReplicated:true
- Closed
- is related to
-
SERVER-31019 Changing fCV during initial sync leads to divergent data across replica set members
- Closed
-
SERVER-31607 Remove FeatureCompatibilityVersionInfo struct
- Closed