You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2015/06/04 04:14:38 UTC

[jira] [Updated] (HIVE-10925) Non-static threadlocals in metastore code can potentially cause memory leak

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

Vaibhav Gumashta updated HIVE-10925:
------------------------------------
    Description: There are many places where non-static threadlocals are used. I can't seem to find a good logic for using them. However, they can potentially result in leaking objects if for example they are created in a long running thread every time the thread handles a new session.  (was: There are many places where non-static threadlocals are used. I can't seem to find a good logic of using them. However, they can potentially result in leaking objects if for example they are created in a long running thread every time the thread handles a new session.)

> Non-static threadlocals in metastore code can potentially cause memory leak
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-10925
>                 URL: https://issues.apache.org/jira/browse/HIVE-10925
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.11.0, 0.12.0, 0.14.0, 1.0.0, 1.2.0, 1.1.0, 0.13
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>
> There are many places where non-static threadlocals are used. I can't seem to find a good logic for using them. However, they can potentially result in leaking objects if for example they are created in a long running thread every time the thread handles a new session.



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