Update docs to specify that the termination signal is a SIGTERM #2760
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm running Nomad v0.5.2. The docs suggest that when the
kill_timeoutis specified, a task is sent a SIGINT.However, I'm seeing my task get a SIGTERM. I have an application trap both a SIGINT and a SIGTERM, and the only signal the application sees is a SIGTERM. This comment by @dadgar also suggests that it's a SIGTERM that gets sent to a task. #522