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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.9, 3.7.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Repl 2018-02-26, Repl 2018-03-12
    • Linked BF Score:
      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

            Assignee:
            vesselina.ratcheva Vesselina Ratcheva
            Reporter:
            vesselina.ratcheva Vesselina Ratcheva
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: