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

Shutdown cmd on primary should ignore PrimarySteppedDown error

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.2 Desired
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Repl 2021-10-18

      Description

      Calling shutdown on a primary can fail with PrimarySteppedDown error if the primary has either:

      1. already stepped down
      2. is currently going through an unconditional stepdown
      3. a new term has been detected

      Instead of having users retry the shutdown command on this error, we should consider having shutdown succeed if 1) has happened, or wait for the concurrent stepdown to complete for 2), 3). 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              jason.chan Jason Chan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated: