aws auto scaling routing

0

Did auto scaling setup and using Step scaling policy to scaleout and scalein. when CPU Max reaches 40 above Scaling is happening and another server came to available also but sometimes request is going to the first server which has high CPU utilization because of that server is crashing. Using round robin in load balancer still its not routing properly. How to solve it?

2개 답변
0

What load balancer are you using? Does it have sticky sessions enabled by any chance?

Some insights - https://aws.amazon.com/premiumsupport/knowledge-center/elb-fix-unequal-traffic-routing/

Sample Tutorial just for you to double check the configs - https://docs.aws.amazon.com/autoscaling/ec2/userguide/tutorial-ec2-auto-scaling-load-balancer.html

profile pictureAWS
답변함 2년 전
  • Using Application load balancer. Stickiness is Disabled in Target group attributes

0

Round Robin means that 2 targets on the ALB will each get every other request. If you want the majority of the requests to go to the new instance (until they're evened out) then you should use Least Outstanding Requests: https://aws.amazon.com/about-aws/whats-new/2019/11/application-load-balancer-now-supports-least-outstanding-requests-algorithm-for-load-balancing-requests/

However, you should also look into why the first instance is crashing when the CPU is only around 40%. See if there's a different resource other than CPU that's your bottleneck (memory, disk, network, artificial application limits, etc). If might be that you can get much better performance by changing instance families to one better suited for your resource requirements

AWS
전문가
답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인