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

Initial sync oplog application does not set oplog visibility on completion

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.1, 4.1.2
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Storage NYC 2018-07-30
    • 15

      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.

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: