[
https://issues.apache.org/jira/browse/HIVE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000896#comment-13000896
]
Chinna Rao Lalam commented on HIVE-1959:
----------------------------------------
In startQuery() of HiveHistory.java QueryInfo object put in to queryInfoMap
and while executing the query QueryInfo object is used after getting from the
queryInfoMap But this object is not removed from the map so these objects are
keep on increasing in the map and resulted the memory leak. This object can be
removed from the map in endQuery() of HiveHistory.java
Same thing is happening for TaskInfo objects also.
The TaskInfo objects can be removed from the map in endTask() of
HiveHistory.java
> 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.5.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
