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

Initial sync oplog application does not set oplog visibility on completion

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.1, 4.1.2
    • Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-07-30
    • 15

    Description

      For correctness and performance reasons, secondaries do not update oplog visibility when write units of work commit, but rather at the end of applying a batch.

      The batch completion logic for initial sync is separate and does not seem to contain an analogous clause.

      This can result in hangs finishing up initial sync.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: