-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
-
Storage 2017-09-11
-
0
This is needed to ensure visibility of the oplog entries that are queried.
- is related to
-
SERVER-30977 Need to sign cluster times for unsharded replica sets
- Closed
- related to
-
SERVER-33812 First initial sync oplog read batch fetched may be empty; do not treat as an error.
- Closed
-
SERVER-30724 Initial sync might miss ops that were in flight when it started
- Closed
-
SERVER-37408 Add afterClusterTime to initial sync collection scans
- Closed
-
SERVER-39607 MongoDB 3.4 should unconditionally use afterOpTime for initial sync oplog fetching
- Closed