SEPURI-SAI-KRISHNA commented on PR #13269:
URL: https://github.com/apache/seatunnel/pull/13269#issuecomment-6911135925

   @DanielLeens Thanks. The bounded attempts are in `f244241898`: each probe 
attempt sets `connectTimeout` and `socketTimeout` to 10 s. Against local test 
servers, a server that never sends the greeting, an unroutable address, and a 
server that accepts the login but never answers a query each end the attempt 
after 10.0 to 10.5 s; without the timeouts all three were still blocked after 
40 s. I did not add `setQueryTimeout`: the socket read timeout already ends a 
query with no answer, and Connector/J cancels a query by opening a second 
connection to send `KILL QUERY`.
   
   After SEZ9's review, `ad5e878aa1` extends this to every test connection: 
`getJdbcConnection()` now has the same connect timeout, a 60 s read timeout, 
and a bounded retry when TiDB closes the connection. The description has the 
details.
   
   CI: the job that runs `TiDBCDCIT` passed in all 7 fork runs of this branch, 
2 of them on this head 
(https://github.com/SEPURI-SAI-KRISHNA/seatunnel/actions/runs/43807514658: 16 
tests on JDK 11 and 17). The same day, that job of #13250, without this change, 
failed in `startUp` with `EOFException`.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to