-
Type: Bug
-
Resolution: Fixed
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Fully Compatible
-
ALL
-
v3.6
-
Repl 2018-01-01
The main oplog visibility refresh loop separates out setting the oplog read timestamp and notifying waiters. Calls coming in via the external API do not. Advancing the read timestamp in that code path causes the refresh loop to believe the oplog timestamp did not advance and thus not notify any waiters.