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

Using applyOps in "local" db does not record oplog entries for other databases

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.7
    • Component/s: Replication
    • None
    • ALL
    • Hide

      suppose we insert and delete the same record from a collection, we may got
      two oplogs. named I and D in the natural order.
      if we do db.runCommand(

      {applyOps:[D, I]}

      ) (plz notice the order), then the record appears in the collection(use db.coll.find()), but no related-oplog inserted into the oplog.rs collection, thus primary and secondary unmatch.

      Show
      suppose we insert and delete the same record from a collection, we may got two oplogs. named I and D in the natural order. if we do db.runCommand( {applyOps:[D, I]} ) (plz notice the order), then the record appears in the collection(use db.coll.find()), but no related-oplog inserted into the oplog.rs collection, thus primary and secondary unmatch.
    • Repl 2016-10-10
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      applyOps in reverse-order makes oplog missing

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            wolf_kdy deyukong
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: