What Are the Three Timeouts of a Listener and What Are the Default Durations?
Table 1 lists the timeout durations of listeners at both Layer 4 and Layer 7.
- For shared load balancers, you can configure and modify the timeout durations for TCP, HTTP, and HTTPS listeners.
- For dedicated load balancers, you can configure and modify the timeout durations for TCP, UDP, HTTP, and HTTPS listeners.
Protocol |
Type |
Description |
Value Range |
Default Timeout Duration |
---|---|---|---|---|
TCP |
Idle Timeout (keepalive_timeout) |
Duration for a connection to keep alive. If no request is received within this period, the load balancer closes the connection and establishes a new one with the client when the next request arrives. |
10s to 4000s |
300s |
UDP |
Idle Timeout (keepalive_timeout) |
10s to 4000s |
Shared load balancers: 10s Dedicated load balancers: 300s |
|
HTTP/HTTPS |
Idle Timeout (keepalive_timeout) |
0s to 4000s |
60s |
|
Request Timeout (client_timeout) |
Duration after which the load balancer closes the connection with the client if the load balancer does not receive a request from the client. |
1s to 300s |
60s |
|
Response Timeout (member_timeout) |
Duration after which the load balancer sends a 504 Gateway Timeout error to the client if the load balancer receives no response after routing a request to a backend server and receives no response after attempting to route the same request to other backend servers
NOTE:
If you have enabled sticky sessions and the backend server does not respond within the response timeout duration, the load balancer returns 504 Gateway Timeout to the clients. |
1s to 300s |
60s |
Feedback
Was this page helpful?
Provide feedbackThank 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