You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction 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
I would like ECS to have a task warmup-time feature that excludes initializing tasks from scaling metrics to avoid overprovisioning.
Which service(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We may encounter a scaling issue when implementing ECS AutoScaling considering CPU-utilization metric. The problem occurs in the following scenario:
Tasks consume high CPU resources during their initialization process
When a new task is added, especially in services with few tasks, its initialization process significantly increases the service's overall CPU utilization
This increased CPU usage triggers AutoScaling to add more tasks unnecessarily, resulting in over-provisioning
EC2 AutoScaling already has a solution for this - a default warmup-time option that excludes new resources from scaling metrics for a certain period after launch.
To solve this issue, I propose adding one of these features:
An option in ECS to exclude newly added tasks from metric collection during their warmup period
A new CloudWatch Metric for AutoScaling that excludes newly added tasks from its calculations
Are you currently working around this issue?
We can use alternative metrics if any were available that are not affected by task initialization.
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.)
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
I would like ECS to have a task warmup-time feature that excludes initializing tasks from scaling metrics to avoid overprovisioning.
Which service(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We may encounter a scaling issue when implementing ECS AutoScaling considering CPU-utilization metric. The problem occurs in the following scenario:
EC2 AutoScaling already has a solution for this - a default warmup-time option that excludes new resources from scaling metrics for a certain period after launch.
To solve this issue, I propose adding one of these features:
Are you currently working around this issue?
We can use alternative metrics if any were available that are not affected by task initialization.
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.)
The text was updated successfully, but these errors were encountered: