All movement of the oplog read timestamp must notify waiters

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2018-01-01
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Daniel Gottlieb (Inactive)
            Reporter:
            Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: