-
Type: Question
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Replication
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.