Autoscaling scale in policy working

0

I have an autoscaling group that works with a target-tracking policy and scales out after my instance hits 75% CPU. But I wanna know how much will it take to scale in or terminate the instance made by the autoscaling group right now it's 25 min which is a lot and can I set a custom time for my instance to be deleted during scale in the process? Thanks

已提問 1 年前檢視次數 309 次
1 個回答
0

Some things to consider:

Since you have configured target tracking on CPU utilization, check the Cloudwatch Alarm TargetTracking-xxx-AlarmLow-<random_string> (or something similar) for the Condition defined. The alarm is not editable and the condition for me is defined as being < some threshold for 15 datapoints over 15 minutes.

Normally the LB deregistration delay is 300 seconds and is defined in target group attributes.

And often there is a slight delay for datapoints / metrics to be reflected in cloudwatch; somewhere around 2-3 minutes.

If you add add this up, it takes around 22-23 minutes for the instance to start shutting down. If the above values match your infra also, the 25 minutes you have reported is sort of normal. In this condition the only thing you can do to reduce the time to inititiate shutdown is to decrease the deregistration delay. But that might affect your inflight connections in the LB.

--Syd

profile picture
Syd
已回答 1 年前

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

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

回答問題指南