-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.19
-
Component/s: Replication
-
None
-
Replication
-
ALL
-
-
15
MongoDB 3.4 uses afterOpTime for its initial sync oplog fetching query if the featureCompatibilityVersion is 3.4. However, this is dead code because the featureCompatibilityVersion is unset when the query is constructed, so it has its default value of 3.2. This afterOpTime is essential when initial syncing from a 3.6 node due to the oplog visibility rules on 3.6, and without it, the initial sync can fail with OplogStartMissing. The afterOpTime should not affect behavior when syncing from a 3.4 or 3.2 node, though this should be tested.
- is related to
-
SERVER-30927 Use readConcern afterClusterTime for initsync oplog queries
- Closed