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

applyOps should propagate oplog application mode

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.0-rc5
    • Replication
    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2017-11-13, Repl 2017-12-04

    Description

      When an applyOps oplog entry is applied, it always sets the "inSteadyStateReplication" flag to true for commands and to the "alwaysUpsert" value for operations.

      This means that an applyOps command with a renameCollection command in it will not cause initial sync to restart.

      We should pass the appropriate OplogApplication::Mode into the applyOps function.

      Attachments

        Issue Links

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: