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

lastOpCommitted being reset on restart can cause sync source cycle

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.9
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Repl 2019-03-11
    • 15

      Consider two nodes in a set, nodes A and B. Node A restarts (resetting its lastOpCommitted to 0) and is ahead of node B. Node B syncs from A. A has no lastOpCommitted so A chooses to sync from B which has a non-zero lastOpCommitted, even though B is already syncing from A.

        1. sync_source_cycle.js
          4 kB
          William Schultz

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: