Rollback can fail if run against a lagged node that catches up

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.4, 4.3.3, 4.0.17
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2, v4.0
    • Repl 2018-06-18, Repl 2018-07-02, Repl 2018-07-16, Repl 2018-07-30, Repl 2019-11-18, Repl 2019-12-02, Repl 2020-01-27
    • 52
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      It is possible to decide to roll back against a sync source that is behind the rollback node (due to receiving an empty batch), then resolve the common point when that same source is ahead. This leads to the rollback node crashing during oplog truncation, as there are no entries after the common point.

            Assignee:
            Siyuan Zhou
            Reporter:
            Vesselina Ratcheva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: