hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16383) Switch to HikariCP as default connection pooling
Date Wed, 05 Apr 2017 22:51:41 GMT

    [ https://issues.apache.org/jira/browse/HIVE-16383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957955#comment-15957955
] 

Prasanth Jayachandran commented on HIVE-16383:
----------------------------------------------

I was suggesting to use the approach in the current patch. I will update the description to
mention how this will affect TxnHandler and how this should be configured in the presence
of multiple metastore hosts and multiple HS2 embedded metastore. With the attached patch,
current behavior is not changed. If required, we can put a separate configs for each or separate
xml files (personally I would prefer this to live in HiveConf - our central place for all
configs).

> Switch to HikariCP as default connection pooling
> ------------------------------------------------
>
>                 Key: HIVE-16383
>                 URL: https://issues.apache.org/jira/browse/HIVE-16383
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 3.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>         Attachments: HIVE-16383.1.patch
>
>
> Since 3.0 is planned to move to JDK8, we can now switch to HikariCP as default connection
pooling for DN because of its improved performance over others. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message