Timeout Durations
You can configure and modify timeout durations for your listeners to meet varied demands.
Listener Timeout Durations
- Idle Timeout (s) is available for Layer 4 (TCP, UDP, and TLS) listeners.
- Idle Timeout (s), Request Timeout (s), and Response Timeout (s) are available for Layer 7 (HTTP, HTTPS, and QUIC) listeners.
Idle Timeout (s)
You can configure the maximum duration during which no data is transferred between the load balancer and a client. If no data is transmitted during this period, the load balancer closes the connection and establishes a new one when the next request is received.
Request Timeout (s)
- The timeout duration for the load balancer to read the request header from the client. If the client does not send a complete request header within this duration, the request is interrupted.
- The maximum interval between two consecutive requests received by the load balancer.
The request timeout does not limit the total transmission duration of a complete request.
Response Timeout (s)
You can configure how long the load balancer waits for a response from a backend server. If the backend server does not respond within the configured timeout, the load balancer retries the request on another backend server. If no backend server responds, the load balancer stops waiting and returns the HTTP 504 error code.
If sticky session is enabled and the load balancer receives no response from the backend server within the response timeout duration, the load balancer does not retry the request and returns the HTTP 504 error code directly.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot