Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
Storage NYC 2018-04-23
-
50
Description
Currently, oplog reads use the oplog visiblity timestamp, but this value is not maintained properly while a batch is being applied.
Attachments
Issue Links
- is duplicated by
-
SERVER-34564 Potential oplog visibility bug replicating from a secondary
-
- Closed
-