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

Optype "db" not handled correctly by applyOperation_inlock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • ALL
    • 0

    Description

      {op: "db"} oplog entries are used to declare the presence of a database. However, applyOperation_inlock() begins to parse them as delete oplog entries, and fails because they do not have an _id field.

      {op: "db"} oplog entries are used in master-slave replication. This leads to log lines like:

      sync: caught user assertion 4 Failed to apply delete due to missing _id: { ns: "test.", op: "db" } while applying op: { ns: "test.", op: "db" }
      

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: