hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vaibhav Gumashta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-7353) HiveServer2 using embedded MetaStore leaks JDOPersistanceManager
Date Mon, 18 Aug 2014 10:19:18 GMT

     [ https://issues.apache.org/jira/browse/HIVE-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vaibhav Gumashta updated HIVE-7353:
-----------------------------------

    Description: 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.
 (was: While using embedded metastore, while creating background threads to run async operations,
HiveServer2 ends up creating new instances of JDOPersistanceManager rather than using the
one from the foreground (handler) thread. Since JDOPersistanceManagerFactory caches JDOPersistanceManager
instances, they are never GCed.)

> 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
>             Fix For: 0.14.0
>
>         Attachments: HIVE-7353.1.patch, HIVE-7353.2.patch, HIVE-7353.3.patch, HIVE-7353.4.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