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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.1, 4.1.2
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Storage NYC 2018-07-30
    • Linked BF Score:
      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

            Assignee:
            daniel.gottlieb Daniel Gottlieb
            Reporter:
            daniel.gottlieb Daniel Gottlieb
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: