Handle SIGTERM and SIGINT with condor_off, allow for off strategies #202
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.
SIGTERM
andSIGINT
will be trapped and mapped to the appropriatecondor_off
command.You can choose strategy by setting the
SHUTDOWN_STRATEGY
environment variable to one ofpeaceful
,graceful
orfast
.graceful
provides 24 hours for jobs to finish.fast
is default for now, matching the current behavior. We could have policy discussion on how for example the RPM should shutdown. For K8s deployments,graceful
with something like this works well: