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

   @SEZ9 Thanks, all six are in `ad5e878aa1`:
   
   1. `getJdbcConnection()` retries the connect for up to 30 s when TiDB 
refuses or closes it.
   2. A stopped TiDB container fails the wait at once, with the end of its log.
   3. Every test connection gets the 10 s connect timeout, from one 
`jdbcProperties(...)` helper. The read timeout is 10 s for the probe and 60 s 
for the test connections, which run DDL.
   4. The probe treats a `RuntimeException` as a failed attempt, like a 
`SQLException`.
   5. The Javadoc names testcontainers 1.21.4 and #13263, as observed behaviour.
   6. `CONTAINER_STARTUP_TIMEOUT` is used by the three containers and as 
`TIDB_QUERY_WAIT`.
   7. From your summary: the timeout now carries the last error, in its message 
and as its cause.
   
   Checked: against a server that closes every connection, the retry made 5 
attempts in 5.4 s (budget 5 s), the first at once, and ended in `SQLException` 
with the last `CommunicationsException` as a cause. On #13263 you asked for 
repeated runs: the `TiDBCDCIT` job passed 7 of 7 times in fork CI (JDK 11 and 
17, all 3 heads).
   


-- 
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