-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Repl 2019-06-17
-
12
SERVER-41178 fixed the timestamp read issue in rollback recovery, but doing timestamp read with unset last applied may also make oplog writes invisible in initial sync.
- is duplicated by
-
SERVER-41558 Make CollectionScan on oplog work without holding database/collection lock
- Closed
- related to
-
SERVER-41558 Make CollectionScan on oplog work without holding database/collection lock
- Closed