Shutdown cmd on primary should ignore PrimarySteppedDown error

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2021-10-18
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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). 

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: