[ECS] [BUG]: Tasks in deactivating state do not show up on container instance tasks
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
ECS tasks stopped due to load balancer health check failure enter "deactivating" state. Our load balancer deregistration delay is 30min which seems to be the time until containers are actually removed.
During that time they do not show up on the container instance and ECS will try to schedule new tasks on that instance. The tasks will keep failing to provision due to insufficient resources.
**Which service(s) is this request for?**
ECS
Contributor guide
Research direction
No files, tests, or code entry points are named. Start by examining ECS behavior for tasks in the "deactivating" state after a load balancer health-check failure and the 30-minute deregistration delay; done means those tasks appear on the container instance and resource-based scheduling no longer attempts to overcommit it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100