Optype "db" not handled correctly by applyOperation_inlock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      {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" }
      

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: