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

Using createIndexes in applyOps with the oplog application mode set on primary should uassert, not fassert

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None
    • Replication
    • ALL
    • 42

    Description

      It's not legal to use the applyOps command to execute createIndexes, and we have a uassert to prevent that. But if we explicitly set the application mode in the applyOps command to InitialSync (probably also recovery or steady-state), we bypass that check and, on the primary, instead hit an fassert. We should uassert in this situation instead.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32952 applyOps does not validate updates

          • Major - P3 - Major loss of function.
          • Backlog

          Bug - A problem which impairs or prevents the functions of the product. SERVER-53674 Do not run applyOps commands in the fuzzer

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-36263 Bypassing operation validation in applyOps should require special privilege

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              matthew.russotto@mongodb.com Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: