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

XMLWordPrintableJSON

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

      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:
              Scott Hernandez (Inactive)
              Reporter:
              Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: