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

Syncing from delayed secondary may trigger fatal assertion

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.4
    • Component/s: Replication
    • Labels:
      None
    • ALL
    • Hide

      1. Modify the replica set to have a delayed secondary.
      2. Reconfig the replica set.
      3. Insert a document on the primary.
      4. Set the other secondary to sync from the delayed secondary.

      Attached is the jstest that reproduces this issue (syncfrom-delayedsecondary.js).

      Show
      1. Modify the replica set to have a delayed secondary. 2. Reconfig the replica set. 3. Insert a document on the primary. 4. Set the other secondary to sync from the delayed secondary. Attached is the jstest that reproduces this issue (syncfrom-delayedsecondary.js).
    • Repl 15 (06/03/16)

      Using rs.syncFrom() to change the sync target for a delayed secondary may trigger a fatal assertion:

      [rsSync] Fatal assertion 34361 OplogOutOfOrder: Attempted to apply an earlier oplog entry (ts: Apr  6 16:39:42:2) when our lastWrittenOptime was (term: 1, timestamp: Apr  6 16:39:42:3)

        1. syncfrom-delayedsecondary.js
          0.7 kB

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            kevin.adistambha@mongodb.com Kevin Adistambha
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: