[SERVER-36908] Shutdown should ignore PrimarySteppedDown on stepdown failure Created: 28/Aug/18  Updated: 06/Dec/22

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

Type: Question Priority: Major - P3
Reporter: Jonathan Reams Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Replication
Participants:

 Description   

We currently ignore NotMaster on shutdown, and now the shutdown command sometimes fails with PrimarySteppedDown: While waiting for secondaries to catch up before stepping down, this node decided to step down for other reasons. Since the primary isn't the primary, we should just ignore this error and continue shutting down so our shutdown code is more reliable.

 



 Comments   
Comment by Shane Harvey [ 04/Sep/18 ]

Very low priority. In https://github.com/10gen/mongo-orchestration/pull/253 I improved mongo-orchestration's shutdown code so that it can handle this case. 

Comment by Tess Avitabile (Inactive) [ 04/Sep/18 ]

shane.harvey, how important is this for mongo-orchestration? This seems reasonable for us to fix, but I would like to know the priority.

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