aws / aws/containers-roadmap

[ECS] [request]: Circuit Breaker

Open
#1,573 1 comment 9 reactions 0 assignees View on GitHub
ECS Proposed
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**
What do you want us to build? A retry count into Circuit Breaker. Once reached, it should go into a failed state

**Which service(s) is this request for?**
Fargate, ECS platform 1_4

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I currently tried this with Circuit Breaker on with Rollback on and off, but if there is an issue with the container being deployed, if you use Cloud Formation, it seems to take quite a bit of time before it fails with the UPDATE_ROLLBACK_COMPLETE state in CF. It seems to try to restart the failed services 10 to 12 times each with a long period of time before the failure occurs. It takes way too long to fail.

**Are you currently working around this issue?**
How are you currently solving this problem?
We need to wait a long period of time for the failure. In excess of 20 minutes.

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Contributor guide

Open the contributing guide

Research direction

The request concerns ECS/Fargate circuit-breaker behavior during CloudFormation deployments. No repository files, tests, or implementation entry points are identified in the issue, so begin by clarifying the ECS platform behavior and the desired retry-count semantics. Done would require an agreed design for reaching a failed state sooner after the configured retry count.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.