ECS Managed Container Instance Scaling Over Provisioning

0

I have an ECS cluster with a capacity provider backed by EC2 container instances and managed autoscaling. The autoscaling group permits scaling to 0 when no tasks are running/requested.

When a task is requested and there are no currently running instances, I'm finding the autoscaling group is provisioning two instances where one would have been fine to fulfill the request. Is anybody else seeing this behaviour? is it expected? This only happens when the ASG desired count is 0 - i.e. there are no requested tasks and no container instances running in the cluster.

1 個回答
0

This is likely due to the scaling policy that is currently configured for your ECS cluster. You can adjust this to scale out more slowly one instance at a time if you wish. Some documentation to help you with this can be found here: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html

AWS
bendutt
已回答 1 年前
  • Thanks for posting. in this case, the scaling configuration is not for ECS. Rather it's for EC2 instances that go on to become ECS container hosts. And it's managed scaling so i can't configure anything myself. I did look at the config through the CLI and I can see the StepAdjustments element is empty.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南