-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Cloud Manager, Ops Manager
-
Labels:
-
Environment:
*Location*: https://docs.cloud.mongodb.com/tutorial/shut-down-deployment/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36
*Referrer*: https://www.google.fr/
*Screen Resolution*: 1280 x 800
*repo*: REPONAME
*source*: tutorial/shut-down-deployment
*Location*: https://docs.cloud.mongodb.com/tutorial/shut-down-deployment/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36 *Referrer*: https://www.google.fr/ *Screen Resolution*: 1280 x 800 *repo*: REPONAME *source*: tutorial/shut-down-deployment
Hello,
This doc is not very clear about how the shutdown behaves when a host isn't responding anymore. Is it equivalent to kill -9 the process locally ?
I am asking this question because we had to "kill -9" a primary several times from our servers in the last few days, because the primary was not responding at all to mongo, mongotop, mongo and mongostat. Killing it and letting the replica set electing a new primary solved the issue every time for us.
Reporter: Romain Péchayre
E-mail: rpechayr@gmail.com