New Rack Param EcsContainerStopTimeout #3747
Merged
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.
What is the feature/update/fix?
Feature: New Rack Parameter for ECS Container Stop Timeout
We have introduced a new rack parameter,
EcsContainerStopTimeout
, that allows you to set a custom timeout duration for stopping ECS containers. This parameter controls the time before ECS issues a SIGKILL after sending a SIGTERM to the container, allowing more time for graceful shutdowns where needed.By default,
EcsContainerStopTimeout
is set to a null value, which means it will defer to the ECS default 30-second stop timeout or any custom configurations already set at the ECS level. This approach ensures that no existing configurations or behaviors are affected unless you explicitly set a value.This parameter can be particularly useful for applications that require extra time to shut down properly, such as those with ongoing user sessions or complex cleanup processes.
For more information, refer to the AWS StopTask Documentation.
How to use it?
To set the
EcsContainerStopTimeout
parameter, use the following command:<value>
can be specified in seconds (s
) or minutes (m
). For example, both60s
and1m
are valid inputs and will set the timeout to 60 seconds.Does it have a breaking change?
There are no breaking changes introduced with this feature.
Requirements
To use this feature, you must be on at least rack version
20241112202208
.You can check your rack's version with the command
convox rack -r rackName
.Update your rack to the latest version with the command
convox rack update -r rackName
.