Stop replication can happen in wrong order for catchup.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
    • Repl 2021-02-22, Repl 2021-03-08, Repl 2021-03-22, Repl 2021-04-05, Repl 2021-04-19
    • 143
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Catchup.js calls stopReplicationAndEnforceNewPrimaryToCatchUp. But we don't enforce the ordering that replication is stopped, so the node that we want to elect could be stopped first, meaning that its data is not fresh enough to be elected.

            Assignee:
            Samyukta Lanka
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: