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

Updates from user-executed "applyOps" can fail in initial sync

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-08-12, Repl 2019-08-26
    • Linked BF Score:
      0

      Description

      When a user executes applyOps with an update on the primary, this is treated as an upsert by default, therefore when the applyOps oplog entry is replayed on the secondary during initial sync it should also be treated as an upsert. However, it is not.

      Fetching missing documents masks this bug, for now (see SERVER-42022). After this change, we no longer fetch missing documents when applying an applyOps oplog entry during initial sync, and initial sync still succeeds.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jesse A. Jesse Jiryu Davis
              Reporter:
              jesse A. Jesse Jiryu Davis
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: