how long will ELB allow inflight requests traffic to continue?

A user has setup connection draining with ELB to allow in-flight requests to continue while the instance is
being deregistered through Auto Scaling. If the user has not specified the draining time, how long will ELB
allow inflight requests traffic to continue?

A user has setup connection draining with ELB to allow in-flight requests to continue while the instance is
being deregistered through Auto Scaling. If the user has not specified the draining time, how long will ELB
allow inflight requests traffic to continue?

A.
600 seconds

B.
3600 seconds

C.
300 seconds

D.
0 seconds

Explanation:
The Elastic Load Balancer connection draining feature causes the load balancer to stop sending new requests
to the back-end instances when the instances are deregistering or become unhealthy, while ensuring that
inflight requests continue to be served. The user can specify a maximum time (3600 seconds. for the load
balancer to keep the connections alive before reporting the instance as deregistered. If the user does not
specify the maximum timeout period, by default, the load balancer will close the connections to the
deregistering instance after 300 seconds.



Leave a Reply 0

Your email address will not be published. Required fields are marked *


Chef

Chef

The maximum timeout value can be set between 1 and 3,600 seconds (the default is 300 seconds). When the maximum time limit is reached, the load balancer forcibly closes connections to the de-registering instance.

C.
300 seconds