hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13129) CliService leaks HMS connection
Date Thu, 25 Feb 2016 17:28:18 GMT

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

Naveen Gangam commented on HIVE-13129:
--------------------------------------

[~aihuaxu] This should only be creating one HMS connection, during HS2 startup, over the lifetime
of the HS2. Do you see this causing an incremental leak? or are you proactively closing that
HMS connection because you think its never used again? 

> CliService leaks HMS connection
> -------------------------------
>
>                 Key: HIVE-13129
>                 URL: https://issues.apache.org/jira/browse/HIVE-13129
>             Project: Hive
>          Issue Type: Sub-task
>          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)

Mime
View raw message