DanielLeens commented on issue #11769: URL: https://github.com/apache/seatunnel/issues/11769#issuecomment-5315842676
Thanks for the new logs. I re-checked the current `dev` JDBC sink path before replying again, and the thread now shows that the issue is broader than only the `connection-test-query` path discussed in PR #11771. That PR still looks like a valid narrow fix for one gap: today `JdbcSinkWriter` applies pool validation before forwarding user `properties`, so a `connection-test-query` inside the `properties` block does not actually configure HikariCP's pool validation path on current `dev`. But the stack you pasted shows a second failure path after the connection is already broken: 1. Hikari marks the connection broken with SQLSTATE `08S01` / MySQL `wait_timeout` symptoms; 2. `JdbcOutputFormat.flush()` enters the reconnect branch and calls `updateExecutor(true)` when it sees connection / statement-closed errors; 3. the retry still ends up at `FieldNamedPreparedStatement.setInt(...)` with `StatementIsClosedException`, wrapped later as `Data type cast failed`. So I would keep PR #11771 scoped as the validation-query prevention fix, but I would not treat it as the full fix for this issue anymore. The current logs now point to a separate reconnect / buffered-row replay gap in the JDBC sink path. The most useful next step would be: 1. keep #11771 limited to the `connection-test-query` prevention path; 2. add a follow-up fix (or extend the same work if the PR author agrees) that reproduces the `08S01 -> reconnect -> statement closed on replay` path with a focused `JdbcOutputFormat` / buffered-executor regression test; 3. update the issue summary in English with whether the failing run is multi-table + `generate_sink_sql = true`, because that helps narrow the replay path. As an operational mitigation, it is still worth keeping Hikari `maxLifetime` / `keepaliveTime` below MySQL `wait_timeout`, but source-wise I think this issue should remain open until the reconnect path is fixed as well. -- 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]
