aws / aws/containers-roadmap

[AWS Batch] [request]: Add stopTimeout option for AWS Batch Job Definition

Open
#2,059 1 comment 8 reactions 0 assignees View on GitHub
Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

It is helpful if we can set stopTimeout for job definition for example, when we use Fargate Spot.

When Fargate Spot termination occurred, container is killed stopTimeout seconds after SIGTERM is sent[1].
So, it is helpful to set stopTimeout when we use Fargate Spot.
However, there is no option for setting stopTimeout in Batch job definition[2].

[1] AWS Fargate capacity providers - Handling Fargate Spot termination notices - https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html#fargate-capacity-providers-termination

[2] Job definition parameters - https://docs.aws.amazon.com/batch/latest/userguide/job_definition_parameters.html

Contributor guide

Open the contributing guide

Research direction

Start with the AWS Fargate capacity provider termination-notice documentation and the AWS Batch job definition parameters reference linked in the issue. Determine the implementation path for exposing stopTimeout in a Batch job definition; done means the option is supported and documented for the stated Fargate Spot use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.