Secondary crashes with oplog stream went back in time

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.5
    • Component/s: Replication
    • None
    • ALL
    • Repl C (11/20/15), Repl D (12/11/15), Repl E (01/08/16), Repl F (01/29/16), Repl 10 (02/19/16), Repl 11 (03/11/16)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We ran into a crash on 3.0.5 where the oplog was reported as going back in time, but the timestamps in the log match

      replication oplog stream went back in time. previous timestamp: 55d25074:41 newest timestamp: 55d25074:41. Op being applied: { ts: Timestamp 1439846516000|65, h: 1280351009425609402, v: 2, op: "i", ns: "...", o: { ... }

        1. db111.gz
          1.88 MB
        2. md3-db1.gz
          492 kB
        3. md3-db2.gz
          42 kB
        4. md3-db2-full.log.tar.gz
          492 kB

            Assignee:
            Eric Milkie
            Reporter:
            Michael Kania
            Votes:
            1 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: