[ 
https://issues.apache.org/jira/browse/HIVE-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shining reassigned HIVE-18278:
------------------------------

    Assignee: shining

> Error in acquiring locks: java.lang.RuntimeException: java.sql.SQLException: 
> Unable to open a test connection to the given database.
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-18278
>                 URL: https://issues.apache.org/jira/browse/HIVE-18278
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 2.3.0
>         Environment: Hive:2.3.0
> MetaStore DB : postgresql
>            Reporter: shining
>            Assignee: shining
>            Priority: Major
>
> Launch a hive cli client, it will be build 4 connections on postgresql,  when 
> hive cli is openned 20 or more, the postgresql connections will be 
> Exhausted(default 100 connections). Then execute the command will be error:
> {noformat}
> hive> show tables;
> FAILED: Error in acquiring locks: java.lang.RuntimeException: 
> java.sql.SQLException:
>               Unable to open a test connection to the given database. 
>               JDBC url = jdbc:postgresql://101.12.4.1:5432/hive, username = 
> hive. 
>               Terminating connection pool (set lazyInit to true if you expect 
> to start your database after your app).
>               Original Exception: ------org.postgresql.util.PSQLException: 
>               FATAL: remaining connection slots are reserved for 
> non-replication superuser connections
> {noformat}
> I also test in hive 1.1, When open a new hive cli, the connection number of 
> pgsql  doesnot increase. Why the hive2.3 occupy 4 connection? Anyone else 
> know this?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to