kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-06 10:25:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

Explain term signal behavior for Docker tasks

Browse Source
This commit is contained in:
Hynek Schlawack
2017-06-16 17:24:54 +02:00
parent 52ffc01972
commit c1777f913e
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
website/source/docs/operating-a-job/update-strategies/handling-signals.html.md
View File

@@ -19,8 +19,11 @@ force-killing it.
Before Nomad terminates an application, it will send the `SIGINT` signal to the
process. Processes running under Nomad should respond to this signal to
gracefully drain connections. After a configurable timeout, the application wil
be force-terminated.
gracefully drain connections. After a configurable timeout, the application
will be force-terminated.
For more details on the `kill_timeout` option, please see the
[job specification documentation](/docs/job-specification/task.html#kill_timeout).
```hcl
job "docs" {
@@ -33,5 +36,7 @@ job "docs" {
}
```
For more detail on the `kill_timeout` option, please see the
[job specification documentation](/docs/job-specification/task.html#kill_timeout).
Please note that the behavior is subtly different for Docker-based tasks. In
this case a `docker stop` command is issued that will send a `SIGTERM` to your
container entry point instead. The `kill_timeout` option is still respected
though.