1 Answer
- Newest
- Most votes
- Most comments
0
*UPDATE:
I was going through some blogs, manuals and documentations and I tried something different: separated the scalein from scaleout policies.
Here's what I changed:
- Disabled SCALE IN from the policy that tracked if the memory was above 90%.
- Created another STEP policy and new alarm, checking if the memory was below 70%. The action is configured to decrease ONE task per time.
It's working that way... I don't think that's the ideal solution and still don't know why the target tracking isn't scaling in. I mean, it's still a very small project, but, once the need for scale out and scale in increases in dozens, the scale in process will be much slower (as it should be, but in this case, it could be much much slower depending on how much tasks scaled out)
I could go back to the previous scenario if anyone come up with something to check and try out.
Thanks again.
answered 2 years ago
Relevant content
- asked 17 days ago
- Accepted Answerasked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
2 quick questions:
Hello Shahad, thank you for your quick response.
1- Yes, it seems that it's the ECS service autoscaling isn't scaling in (tasks). The CP/ASG is scaling in as expected (when a EC2 instance is with 0 tasks running, that is, the CapacityProviderReservertion is below 100%). 2- I read about it, but there was* only one target tracking policy in place. (update below)