-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow setting graceful termination timeout for each task #522
Comments
Yeah that is a possibility. Nomad already does this. It first does a SIGTERM and then a SIGKILL but the period is not user specifiable currently. Do you need it to be configurable or you just want the soft kill then hard kill behavior? |
I would love to be able to configure the timeout, because some tasks might take a bit longer to clean up (hence a longer timeout). |
This is a duplicate of #17 |
Fixed by #624 |
Thee docs suggest that when the `kill_timeout` is specified, a task is sent a SIGINT. However, I'm seeing my task get a SIGTERM. This comment by @dadgar also suggests that it's a SIGTERM that gets sent to a task. hashicorp#522
The docs suggest that when the `kill_timeout` is specified, a task is sent a SIGINT. However, I'm seeing my task get a SIGTERM. This comment by @dadgar also suggests that it's a SIGTERM that gets sent to a task. hashicorp#522
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
It would be nice if we could set a custom timeout for terminating tasks.
For example, I might have a task (running in docker) that provides an api for other services and takes a while to clean up on termination. I would like to be able to do the following:
The text was updated successfully, but these errors were encountered: