[
https://issues.apache.org/jira/browse/HIVE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007928#comment-13007928
]
Edward Capriolo commented on HIVE-1959:
---------------------------------------
While WeakHashMap may work logically it may not be our best option. If we only
find one instance of a class in the entire code base I generally believe that
is breaking some un-established internal coding standards and introducing a
behaviour that is not in line with the rest of the systems. (A two mile view)
> Potential memory leak when same connection used for long time. TaskInfo and
> QueryInfo objects are getting accumulated on executing more queries on the
> same connection.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-1959
> URL: https://issues.apache.org/jira/browse/HIVE-1959
> Project: Hive
> Issue Type: Bug
> Components: Server Infrastructure
> Affects Versions: 0.8.0
> Environment: Hadoop 0.20.1, Hive0.5.0 and SUSE Linux Enterprise
> Server 10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5).
> Reporter: Chinna Rao Lalam
> Assignee: Chinna Rao Lalam
> Attachments: HIVE-1959.patch
>
>
> *org.apache.hadoop.hive.ql.history.HiveHistory$TaskInfo* and
> *org.apache.hadoop.hive.ql.history.HiveHistory$QueryInfo* these two objects
> are getting accumulated on executing more number of queries on the same
> connection. These objects are getting released only when the connection is
> closed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
