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

resync command should set STARTUP2 after stopping data replication

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • ALL
    • Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06

    Description

      Currently it sets follower mode to STARTUP2 before stopping data replication. This can lead to a race with the data replication threads which also set the follower mode. If they set the follower modes after the resync command, we would be doing an initial sync in a different follower mode.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: