-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
Ever since we've upgraded to 3.2.10 - when running db.shutdownServer() - we constantly get:
shutdownServer failed: { "ok" : 0, "errmsg" : "No electable secondaries caught up as of 2016-11-14T06:51:05.073+0000. Please use {force: true} to force node to step down.", "code" : 50 }
- There are 2 very "tight" secondaries with 0-2 replication lag
- rs.stepDown() works, so we have to stepDown and only then shutdown the server
- related to
-
SERVER-27118 Default shutdown command's 'timeoutSecs' argument to 10 seconds
- Closed