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/03/02 15:43:18 UTC
[jira] [Updated] (HIVE-13129) CliService leaks HMS connection
[ https://issues.apache.org/jira/browse/HIVE-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aihua Xu updated HIVE-13129:
----------------------------
Attachment: HIVE-13129.2.patch
Talked to Chaoyu offline. He is planning to use the connection for delegation token.
So patch-2 moves the closure to the stop() method. The resources would be released eventually when the HS2 closes, but seems still a good idea to close them immediately when it's no use especially for the case of multiple HS2 instances.
> 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.2.patch, 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)