How to understand jdbc disconnected pipes
In this issue, the editor will bring you about how to understand the disconnected channels of jdbc. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.
18Rd 34INFO o.a.http.impl.execchain.RetryExec 50.032 [pool-11-thread-10] INFO o.a.http.impl.execchain.RetryExec-I exception O exception (java.net.SocketException) caught when processing request to {}-> http://35.26.59.191:8123: > disconnected conduit 18Rd 34INFO o.a.http.impl.execchain.RetryExec 50.033 [pool-11-thread-10] INFO o.a.http.impl.execchain.RetryExec-Retrying request to {}-> http://35.26.59.191:8123
If we set the socketTimeout as follows:
SocketTimeout=60000; this means that the server must start spitting data to the client within 60 seconds to keep the socket active. Configure to 60 seconds, the general query will not encounter problems. Even if it is a large query such as a full table scan, the data will continue to spit out to the client without reaching the 60-second limit.
However, for large queries with ORDER BY, DISTINCT, COUNT, SUM and other methods, they will probably not calculate the result within 60 seconds. At this time, the client will detect the socket timeout and automatically disconnect, causing the server to receive the QUERY_KILL and abort the execution.
Conclusion: for large queries with sorting and aggregation functions, socketTimeout should set a large value. For example:
SocketTimeout=6000000
The above is the editor for you to share how to understand the disconnected channel of jdbc, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.
