[ECS] [issue]: service connect draining time
- 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?
My team and I have been working on implementing Amazon Service Connect. Currently, we have one cluster that hosts many services. I want to use AWS Service Connect to connect these services together in ECS Fargate. However, I am encountering an issue during the implementation process. I updated the AWS ECS service, task creating time is so long, and task draining time is also so long. How to solve this issue I want to do a fast deployment old service to update the service how can I reduce deployment delay time? last week, I migrated app mesh to Service Connect.
**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR
ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
**Are you currently working around this issue?**
How are you currently solving this problem?
**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
Research direction
Start with the reported ECS Service Connect deployment on Fargate, including the long task-creation and draining times after migrating from App Mesh. Compare the deployment behavior with the desired faster update and determine what concrete Service Connect or ECS change would be required; the issue provides no reproduction details, files, tests, or completion criteria.
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
- Needs clarification
- Newbie friendliness
- 18/100