ECS Managed Container Instance Scaling Over Provisioning

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.

주제

관리 및 거버넌스 컨테이너 컴퓨팅

태그

AWS Auto Scaling 아마존 엘라스틱 컨테이너 서비스 아마존 EC2 Auto Scaling

언어

English

rePost-User-9358417

질문됨 일 년 전438회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

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

bendutt

답변함 일 년 전

rePost-User-9358417
일 년 전
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.

ECS Managed Container Instance Scaling Over Provisioning

관련 콘텐츠