You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Aihua Xu (JIRA)" <ji...@apache.org> on 2016/02/24 17:38:18 UTC

[jira] [Commented] (HIVE-13129) CliService leaks HMS connection

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

Aihua Xu commented on HIVE-13129:
---------------------------------

Attach the patch-1: we will close the HMS connection right after getting authorization policy since we are not using the connection in that service main thread anymore. All the incoming queries will be handled by thread pool and will use separate HMS connections.

> CliService leaks HMS connection
> -------------------------------
>
>                 Key: HIVE-13129
>                 URL: https://issues.apache.org/jira/browse/HIVE-13129
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 2.1.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-13129.patch
>
>
> HIVE-12790 fixes the HMS connection leaking. But seems there is one more connection from CLIService.
> The init() function in CLIService will get info from DB but we never close the HMS connection for this service main thread.  
> {noformat}
>     // creates connection to HMS and thus *must* occur after kerberos login above
>     try {
>       applyAuthorizationConfigPolicy(hiveConf);
>     } catch (Exception e) {
>       throw new RuntimeException("Error applying authorization policy on hive configuration: "
>           + e.getMessage(), e);
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)