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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL
    • Linked BF Score:
      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

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: