Handle for SIGTERM #561
Open
Handle for SIGTERM #561
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
shayonj
force-pushed
the
s/term-sginal
branch
7 times, most recently
from
f4272ed
to
581e40e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In containerized workloads, it's common to receive a
SIGTERMsignal when a pod or task is shutting down. Currently, when this occurs, theraketask throws aSignalExceptionand returns a status code of1. This behavior can be misinterpreted by container orchestration systems (like Fargate, Kubernetes, etc.) as an error, rather than a graceful exit.This PR proposes that, when a
SIGTERMsignal is received by araketask, it should return an exit code of143. This exit code is the standard response for aSIGTERM, indicating a proper shutdown was acknowledged and handled gracefully.I only added this for SIGTERM, but should be extensive for other handlers too if needed in future.
Related: #272