[
https://issues.apache.org/jira/browse/FLINK-19691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu updated FLINK-19691:
----------------------------
Summary: Support connection.max-retry-timeout configuration for JDBC
connector (was: Expose `CONNECTION_CHECK_TIMEOUT_SECONDS` as a configurable
option in Jdbc connector)
> Support connection.max-retry-timeout configuration for JDBC connector
> ---------------------------------------------------------------------
>
> Key: FLINK-19691
> URL: https://issues.apache.org/jira/browse/FLINK-19691
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC, Table SQL / Ecosystem
> Affects Versions: 1.11.0
> Reporter: hailong wang
> Assignee: jiawen xiao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> Jdbc connector can check whether the connection is valid, and the timeout is
> 60 second [FLINK-16681].
> But the fixed timeout of 60 second sometimes too long to wait. In some
> scenes, I just want to wait for 5 second and fast failed and restarting if
> it is still invalid.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
