Allow for shorter graceful shutdown #61
Merged
Conversation
This file contains hidden or 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 healthcheck_interval env-var allows a user to specify a shorter time before shutting down the HTTP server to new connections. This change has been tested upstream in the of-watchdog which wraps this template. The default behaviour is to continue to use the write_timeout for a safe shutdown duration. Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
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.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com
Description
Allow for shorter graceful shutdown
How Has This Been Tested?
The healthcheck_interval env-var allows a user to specify a
shorter time before shutting down the HTTP server to new
connections.
This change has been tested upstream in the of-watchdog which
wraps this template.
How are existing users impacted? What migration steps/scripts do we need?
The default behaviour is to continue to use the write_timeout
for a safe shutdown duration.