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.

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ