- 最新
- 最多得票
- 最多評論
Hello.
What exactly are the criteria for an ALB to be considered unhealthy? Is it related to to the health of associated target groups? If so, how does it work for ALBs with more than one target group?
We determine whether it is normal by checking the health of the target group linked to the ALB.
Also, if multiple target groups are configured, all target groups will be used to determine health.
https://repost.aws/knowledge-center/load-balancer-marked-unhealthy
When all the target groups in an Application Load Balancer are healthy, Route 53 marks the alias record as "healthy." To pass the target group health check, the number of healthy targets much reach the defined thresholds in your target group attributes. Route 53 then returns records according to your routing policy. For example, if you use latency-based routing, then Route 53 returns the least latent record from your DNS client or resolver's location.
Is it possible to view the current health status for a record/ALB?
Since we are checking the health of the target group, there are probably no metrics for Route53.
相關內容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
If you use Route 53 to route DNS queries to your load balancer, you can also configure DNS failover for your load balancer using Route 53. In a failover configuration, Route 53 checks the health of the target group targets for the load balancer to determine whether they are available. If there are no healthy targets registered with the load balancer, or if the load balancer itself is unhealthy, Route 53 routes traffic to another available resource, such as a healthy load balancer or a static website in Amazon S3.