Description:
Many users have reported a network issue where they see a large number of connections in TIME_WAIT and IDLE states. This indicates that the connections are not being closed properly by the server or the client.
When I analyzed the network traffic, I found that the server was sending HTTP Error 513 to the client, which means that the server is overloaded and cannot handle more requests. The client was also logging a socket close event, which means that the client was terminating the connection.
This can be simulated using Jmeter. The HTTP error code 153 resulted from the max concurrent connection limit reached, and the allowed queue was also full.
This issue can cause performance degradation and resource wastage on both the server and the client. To resolve this issue, we recommend the following steps:
Resolution:
1. Investigate the process of holding onto the connection longer than necessary.
2. Increase the server capacity or scale up the server to handle more concurrent requests. In other words, increase the maximum concurrent connection limit and queue.
3. For a better troubleshooting experience, configure the server to send an intuitive HTTP response code instead of 513, such as 503 (Service Unavailable) or 429 (Too Many Requests).
4. Configure the TCP parameters on both the server and the client to reduce the TIME_WAIT and IDLE timeout values.
Happy system maintenance!
Comments
Post a Comment