Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-32397

All movement of the oplog read timestamp must notify waiters

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker - P1
    • Resolution: Fixed
    • None
    • 3.6.1, 3.7.1
    • Replication, Storage
    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2018-01-01

    Description

      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.

      Attachments

        Activity

          People

            daniel.gottlieb@mongodb.com Daniel Gottlieb
            daniel.gottlieb@mongodb.com Daniel Gottlieb
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: