[HIVE-27756] expose Lifetime in HikariConfig

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Standalone Metastore
• Labels: pull-request-available

Environment

hive-2.3.4+,

hikaricp-2.5.1+;

postgres 13.0

pgbouncer 1.17

• Assignee: Mingmin Xu
• Reporter: Mingmin Xu
• Created: 28/Sep/23 23:42
• Updated: 11/Dec/23 00:20

Description

We run into an issue with HikariCP on Postgres with PgBouncer, that the connection in local pool is expired already, temporally we move to none_cp mode to mitigate the issue. By exposing maxLifetime in HikariConfig, we would be able to fix it.

Regarding to the issue:

• PgBouncer has one conf server_lifetime, named as T0, to expire long idle connections;

•  HikariCP has maxLifetime with default as 1800_s, named as T1;

When T1 > T0, HMS connection_pool would hold connections which is expired by pgbouncer already. For operation reasons, we prefer to keep a short conn_lifetime instead of increasing T0.

Issue Links

• links to: GitHub Pull Request #4765