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

Execution of replSetStepDown can race with unconditional stepdown via heartbeat response

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.9, 3.7.3
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2018-02-26, Repl 2018-03-12
    • 0

    Description

      Successful executions of unconditional stepdowns supercede stepdown attempts in response to replSetStepDown, but the execution of the command will not be killed if it wasn't issued by a client. Nodes attempting a priority takeover in pv0 send this command to the primary. A possible solution might be to make TopologyCoordinator::prepareForStepDownAttempt return an error if a stepdown has already completed (in addition to the existing stepdown-in-progress check.)

      Attachments

        Activity

          People

            vesselina.ratcheva@mongodb.com Vesselina Ratcheva
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: