Why is my autoscaling group instance unhealthy?

I'm noticing a very strange issue with an AWS auto-scaling group.

Instances are being reported (incorrectly) as being unhealthy. The instances are then being terminated and replaced unnecessarily. This is causing problems because it is leaving the ASG with insufficient capacity to cope with the load.

To try to identify the problem, I've temporarily suspended the "Terminate" process for the ASG.

Right at the moment I have a single instance in the group reported by the ASG as being unhealthy. Logging in to the instance and testing the health check directly proves that it is in fact healthy.

Additionally, the load balancers associated with the ASG also report all instances as healthy.

My question is. How can my ASG consider an instance to be "UNHEALTHY", if the health check type for the group is set to "ELB", and the load balancers report the instance as healthy?

Is there a way I can find out when and why the ASG flagged the instances as "Unhealthy"?

This ASG is currently associated with 2 classic ELB's, and 2 ALB Target Groups. We're in the process of migrating from ELB to ALB.

As mentioned though, both ELB's, and both Target Groups report all instances as healthy.

1
задан 5 March 2019 в 09:05
1 ответ

Supongo que los problemas provienen de tener la instancia como parte de múltiples ELB / ALB TG. Sospecho que cualquiera de esos ELB / ALB puede activar la terminación de la instancia si lo considera insalubre por cualquier motivo.

Cambie el tipo de verificación de estado a EC2 hasta que ' Termine con la migración.

La mejor práctica es tener ASG enlazado a un solo balanceador de carga .

Espero que ayude :)

1
ответ дан 3 December 2019 в 23:06

Теги

Похожие вопросы