Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27015

db.shutdownServer doesn't find electable secondaries

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 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

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            yonido Yoni Douek
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: