具有粘性会话的弹性负载均衡器是否检查健康状况？
does elastic load balancer with sticky sessions check for health?
我正在开发聊天应用程序，出于某些原因，我虽然在 aws 上配置 elastic load balancer 以使用粘性会话。
负载均衡器是否在粘性会话的情况下检查请求所需的服务器的健康状况，或者因为负载均衡器使用粘性会话它不关心服务器的健康状况，因为它不需要任何不同的路由 ?
负载均衡器在路由任何新请求之前确实关心服务器的健康状况。
If an instance fails or becomes unhealthy, the load balancer stops
routing requests to that instance, and chooses a new healthy instance
based on the existing load balancing algorithm. The request is routed
to the new instance as if there is no cookie and the session is no
longer sticky.
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html
还有一个连接耗尽选项，它允许您将正在进行的请求路由到新服务器。
To ensure that a Classic Load Balancer stops sending requests to
instances that are de-registering or unhealthy, while keeping the
existing connections open, use connection draining. This enables the
load balancer to complete in-flight requests made to instances that
are de-registering or unhealthy.
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html
我正在开发聊天应用程序，出于某些原因，我虽然在 aws 上配置 elastic load balancer 以使用粘性会话。
负载均衡器是否在粘性会话的情况下检查请求所需的服务器的健康状况，或者因为负载均衡器使用粘性会话它不关心服务器的健康状况，因为它不需要任何不同的路由 ?
负载均衡器在路由任何新请求之前确实关心服务器的健康状况。
If an instance fails or becomes unhealthy, the load balancer stops routing requests to that instance, and chooses a new healthy instance based on the existing load balancing algorithm. The request is routed to the new instance as if there is no cookie and the session is no longer sticky.
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html
还有一个连接耗尽选项，它允许您将正在进行的请求路由到新服务器。
To ensure that a Classic Load Balancer stops sending requests to instances that are de-registering or unhealthy, while keeping the existing connections open, use connection draining. This enables the load balancer to complete in-flight requests made to instances that are de-registering or unhealthy.
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html