hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7353) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager
Date Thu, 28 Aug 2014 06:25:59 GMT

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

Lefty Leverenz commented on HIVE-7353:
--------------------------------------

This adds configuration parameters *hive.server2.thrift.worker.keepalive.time* and *hive.server2.thrift.http.worker.keepalive.time*
so they need to be documented in the wiki, preferably after these related parameters:

* [Configuration Properties -- HiveServer2 -- hive.server2.thrift.max.worker.threads | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.server2.thrift.max.worker.threads]
* [Configuration Properties -- HiveServer2 -- hive.server2.thrift.http.max.worker.threads
| https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.server2.thrift.http.max.worker.threads]

> HiveServer2 using embedded MetaStore leaks JDOPersistanceManager
> ----------------------------------------------------------------
>
>                 Key: HIVE-7353
>                 URL: https://issues.apache.org/jira/browse/HIVE-7353
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 0.13.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>              Labels: TODOC14
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7353.1.patch, HIVE-7353.2.patch, HIVE-7353.3.patch, HIVE-7353.4.patch,
HIVE-7353.5.patch, HIVE-7353.6.patch, HIVE-7353.7.patch, HIVE-7353.8.patch, HIVE-7353.9.patch
>
>
> While using embedded metastore, while creating background threads to run async operations,
HiveServer2 ends up creating new instances of JDOPersistanceManager which are cached in JDOPersistanceManagerFactory.
Even when the background thread is killed by the thread pool manager, the JDOPersistanceManager
are never GCed because they are cached by JDOPersistanceManagerFactory.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message