I have three mongoD instances running in a replica set in windows. MD1 -> Primary, MD2-> Secondry, MD3-> Secondry settings.electionTimeoutMillis = 10 seconds.

If I bring my primary MongoD instance MD1 down; MD2 and MD3 remains secondary even after 10 seconds. As per mongoDB document, "the primary node was unavailable for longer than the configured timeout and triggers the automatic failover process. One of the remaining secondaries calls for an election to select a new primary and automatically resume normal operations" but in my case MD2 and MD3 remains secondary even after 10 seconds. https://docs.mongodb.com/manual/core/replica-set-elections/#replica-set-elections

migrated from stackoverflow.com Aug 1 '18 at 22:06

This question came from our site for professional and enthusiast programmers.

  • Please post the output of rs.status() before and after the primary is offline, and also the output of rs.conf() – kevinadi Aug 6 '18 at 6:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy