[SERVER-2972] Increase the Upstart script kill timeout Created: 20/Apr/11 Updated: 12/Jul/16 Resolved: 31/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew R | Assignee: | Joe Miklojcik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu or Debian with Upstart |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
When stopping a service managed by Upstart, it uses a default kill timeout of 5 seconds. It sends the service a TERM signal, and if it doesn't stop in 5 seconds it does a hard stop with the KILL signal. 5 seconds is often not enough time for MongoDB to stop (this is often the case for us). It's probably worthwhile to override the default in the packaged /etc/init/mongodb.conf and set it to several minutes or indefinite to be safe. Here's info on kill timeout in the Upstart docs: |
| Comments |
| Comment by Joe Miklojcik [ 31/May/11 ] |
|
Changes that upped this constant to 300 had already been comitted by Kreuter on Mar 17 2011. |