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

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • ALL
    • 42

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: