[SERVER-60673] Shutdown cmd on primary should ignore PrimarySteppedDown error Created: 13/Oct/21  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jason Chan Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-60699 Investigate more frequent occurences ... Closed
Assigned Teams:
Replication
Sprint: Repl 2021-10-18
Participants:

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


Generated at Thu Feb 08 05:50:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.