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

Stop replication can happen in wrong order for catchup.js

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • ALL
    • Repl 2021-02-22, Repl 2021-03-08, Repl 2021-03-22, Repl 2021-04-05, Repl 2021-04-19
    • 143

    Description

      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.

      Attachments

        Activity

          People

            samy.lanka@mongodb.com Samyukta Lanka
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: