[ https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668122#comment-16668122 ]
Jason Dere commented on HIVE-20834: ----------------------------------- Patch to just fetch the ValidTxnWriteIdList upfront when creating the results cache entry, rather than trying to defer the call to fetch the ValidTxnWriteIdList. Looked at heap dumps before/after this patch and the results cache entry is no longer hanging onto a reference to the SemanticAnalyzer. [~jcamachorodriguez] [~gopalv] can you review? > Hive QueryResultCache entries keeping reference to SemanticAnalyzer from > cached query > ------------------------------------------------------------------------------------- > > Key: HIVE-20834 > URL: https://issues.apache.org/jira/browse/HIVE-20834 > Project: Hive > Issue Type: Bug > Reporter: Jason Dere > Assignee: Jason Dere > Priority: Major > Attachments: HIVE-20834.1.patch, dominator_tree.png > > > QueryResultCache.LookupInfo ends up keeping a reference to the > SemanticAnalyzer from the cached query, for as long as the cached entry is in > the cache. We should not be keeping the SemanticAnalyzer around after the > query is done executing since they can hold on to quite a bit of memory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)