`connectionTimeout` parameter for Hikari JDBC con...
# replication-troubleshooting
m
connectionTimeout
parameter for Hikari JDBC connection can be changed if we change the JDBC url Params from UI of Postgres source Connector ? https://github.com/airbytehq/airbyte/pull/15226, If yes How can I check whether it successfully overrides the default value`connectionTimeout = 10000ms` or not?
u
Hi Manish, were you able to test this out in the UI?
m
Hi @Nataly Merezhuk (Airbyte) I pass the ConnectTimeout=60 from UI, But I am still getting
"HikariPool-1 - Connection is not available, request timed out after 10038ms".
which means ConnectionTimeout parameter for Hikarpool is not being overridden.
n
I think you've got a small error, it should be
connectTimeout
not
connectionTimeout
. From the docs: The connector now supports
connectTimeout
and defaults to 60 seconds. Setting connectTimeout to 0 seconds will set the timeout to the longest time available. https://docs.airbyte.com/integrations/sources/postgres/#step-2-set-up-the-postgres-connector-in-airbyte
m
ConnectTimeout is used by postgres which I am using as JDBC url param and passing from UI, while ConnectionTimeout is used by Hikari Pool, both are different. Please check this link https://github.com/airbytehq/airbyte/pull/15226
Also the documentation hasn’t been updated, because if you see the changelogs for postgres connector, now the default is just 10 sec instead of 1 min
image.png
So the timeout error I am getting is because of Hikari-pool so I wanted to increase that. According to this link https://github.com/airbytehq/airbyte/pull/15226 I should be able to override the Hikaripool
ConnectionTimeout
value by `ConnectTimeout`from UI but it’s not overriding and I am still getting error.
n
Thank you for the details, and my apologies for missing that! I think this warrants filing a GitHub issue. Could you do that and link it here? I'll triage it to the appropriate team