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

Check in logOp that we don't record out of order oplog entries

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl F (01/29/16)

      Add check to logOp, logOps to make sure that replCoord->myLastOptime is less than the new one(s) being recorded.

      This used to be checked in 2.6: https://github.com/mongodb/mongo/blob/v2.6/src/mongo/db/repl/oplog.cpp#L267

            Assignee:
            scotthernandez Scott Hernandez (Inactive)
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: