Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-27756

expose Lifetime in HikariConfig

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • Standalone Metastore
    • hive-2.3.4+,

      hikaricp-2.5.1+;

      postgres 13.0

      pgbouncer 1.17

    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.

      Attachments

        Issue Links

          Activity

            People

              mingmxu Mingmin Xu
              mingmxu Mingmin Xu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: