[
https://issues.apache.org/jira/browse/HIVE-29513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HIVE-29513:
----------------------------------
Labels: pull-request-available (was: )
> Increase HikariCP connection timeout default from 30s to 60s
> ------------------------------------------------------------
>
> Key: HIVE-29513
> URL: https://issues.apache.org/jira/browse/HIVE-29513
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Affects Versions: 4.2.0
> Reporter: Riju Trivedi
> Assignee: Riju Trivedi
> Priority: Major
> Labels: pull-request-available
>
> When the Metastore experiences high load or temporary spikes in database
> connection demand, HMS client requests fail with connection timeout errors.
> The current default connection timeout of 30 seconds is insufficient for
> scenarios where:
> * The connection pool is exhausted due to temporary load spikes
> * Database response times are elevated
> {code:java}
> MetaException(message:HikariPool-1 - Connection is not available, request
> timed out after 30000ms.)
> Caused by: java.sql.SQLTransientConnectionException: HikariPool-1 -
> Connection is not available, request timed out after 30000ms.
> at
> com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:602)
> at
> com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:195){code}
> To have enough tolerance on temporary surges on HMS side we should increase
> the timeout to 60 seconds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
