lastOpCommitted being reset on restart can cause sync source cycle

XMLWordPrintableJSON

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

      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.

              Assignee:
              Siyuan Zhou
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: