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

Secondary crashes with oplog stream went back in time

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Incomplete
    • 3.0.5
    • None
    • 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)

    Description

      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: { ... }
      

      Attachments

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

        Issue Links

          Activity

            People

              milkie@mongodb.com Eric Milkie
              dynamike Michael Kania
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: