-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
None
-
Fully Compatible
-
ALL
-
-
Repl 2017-10-02, Repl 2017-10-23
-
0
The node performing the initial sync appears to be able to retain the documents that were inserted prior to the collection being dropped and re-created after changing the featureCompatibilityVersion to 3.6. This issue is related to UUIDs and their impact on oplog application, and therefore doesn't affect the 3.2 or 3.4 branches.
2017-09-10T19:21:06.495-0400 The following documents are missing on the primary: 2017-09-10T19:21:06.495-0400 { "_id" : "while in fCV=3.4" } ... 2017-09-10T19:21:06.498-0400 checkReplicatedDataHashes, the primary and secondary have a different hash for the test database: { 2017-09-10T19:21:06.498-0400 "master" : { 2017-09-10T19:21:06.499-0400 "host" : "hanamizu:20010", 2017-09-10T19:21:06.499-0400 "collections" : { 2017-09-10T19:21:06.499-0400 "mycoll" : "09aabf5621c57d91db16b98b365d8e65" 2017-09-10T19:21:06.499-0400 }, 2017-09-10T19:21:06.499-0400 "md5" : "2105eeb0b1ec2ade59f08fa1f3f40ba9", 2017-09-10T19:21:06.499-0400 "timeMillis" : 0, 2017-09-10T19:21:06.499-0400 "ok" : 1, 2017-09-10T19:21:06.499-0400 "operationTime" : Timestamp(1505085665, 18) 2017-09-10T19:21:06.499-0400 }, 2017-09-10T19:21:06.499-0400 "slaves" : [ 2017-09-10T19:21:06.499-0400 { 2017-09-10T19:21:06.500-0400 "host" : "hanamizu:20011", 2017-09-10T19:21:06.500-0400 "collections" : { 2017-09-10T19:21:06.500-0400 "mycoll" : "b8b6211fb0b559d95ae6df5cc4071420" 2017-09-10T19:21:06.500-0400 }, 2017-09-10T19:21:06.500-0400 "md5" : "072bbaef3649d98b3270e6a2a6eac21f", 2017-09-10T19:21:06.500-0400 "timeMillis" : 0, 2017-09-10T19:21:06.500-0400 "ok" : 1, 2017-09-10T19:21:06.500-0400 "operationTime" : Timestamp(1505085665, 18) 2017-09-10T19:21:06.500-0400 } 2017-09-10T19:21:06.500-0400 ] 2017-09-10T19:21:06.500-0400 }
- is depended on by
-
SERVER-31189 fassert if feature compatibility version changes during rollback
- Closed
- is duplicated by
-
SERVER-31102 Clone admin.system.version first in initial sync, fail sync if FCV changes
- Closed
-
SERVER-86142 Handle FCV change during initial sync while copying collections with recordIdsReplicated:true
- Closed
- is related to
-
SERVER-31384 applyOps should propagate oplog application mode
- Closed
- related to
-
SERVER-31387 oplog application conflates upserting with being in steady state replication
- Closed
-
SERVER-28151 Authentication database should be synced first during an initial sync
- Closed
-
SERVER-31254 Fail initial sync if fCV targetVersion is set or if there is no fCV document
- Closed