-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
-
Repl 2017-10-02
We should fail initial sync if the featureCompatibilityVersion changes in the middle of it, to avoid potential data corruption due to mismatches in the use of UUIDs between the source and destination node. To do this, we should make sure that the very first collection we clone is admin.system.version, so that we know the FCV of the sync source at the beginning of initial sync. Then during initial sync oplog application, we should fail and restart initial sync if we replicate a change to the FCV.
- duplicates
-
SERVER-31019 Changing fCV during initial sync leads to divergent data across replica set members
- Closed
- is related to
-
SERVER-49748 Initial sync should clone admin.system.version before any other collections
- Closed
- related to
-
SERVER-28151 Authentication database should be synced first during an initial sync
- Closed