[
https://issues.apache.org/jira/browse/IMPALA-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844538#comment-16844538
]
Todd Lipcon commented on IMPALA-6876:
-------------------------------------
Seems like the simplest fix here would be to use weak references from this data
structure
> Entries in CatalogUsageMonitor are not cleared after invalidation
> -----------------------------------------------------------------
>
> Key: IMPALA-6876
> URL: https://issues.apache.org/jira/browse/IMPALA-6876
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 3.0, Impala 2.12.0
> Reporter: Dimitris Tsirogiannis
> Priority: Major
> Labels: memory-leak, ramp-up
>
> The CatalogUsageMonitor in the catalog maintains a small cache of references
> to tables that: a) are accessed frequently in the catalog and b) have the
> highest memory requirements. These entries are not cleared upon server or
> table invalidation, thus preventing the GC from collecting the memory of
> these tables. We should make sure that the CatalogUsageMonitor does not
> maintain entries of tables that have been invalidated or deleted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
