[DOCS-6715] clear about how the shutdown behaves when a host isn't resHow does shutdown behave when host isn't responding Created: 03/Dec/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Romain Pechayre | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.cloud.mongodb.com/tutorial/shut-down-deployment/ |
||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | docs-troubleshooting |
| Description |
|
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 |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |
| Comment by Romain Pechayre [ 03/Dec/15 ] |
|
Thank you. I have now. I believe the support ticket are private, but I've referenced this one in the other one. Regards, |
| Comment by Bob Grabar [ 03/Dec/15 ] |
|
rpechayr, Can you also file a support ticket at https://cloud.mongodb.com/support? |