resync command should set STARTUP2 after stopping data replication

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: