[
https://issues.apache.org/jira/browse/IMPALA-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell updated IMPALA-14724:
-----------------------------------
Summary: Consider configuration to use soft values for cache in
CatalogdMetaProvider (was: Consider configuration to use weak values for cache
in CatalogdMetaProvider)
> Consider configuration to use soft values for cache in CatalogdMetaProvider
> ---------------------------------------------------------------------------
>
> Key: IMPALA-14724
> URL: https://issues.apache.org/jira/browse/IMPALA-14724
> Project: IMPALA
> Issue Type: Task
> Components: Catalog
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Priority: Major
>
> CatalogdMetaProvider caches metadata objects inside an Impala daemon inside a
> Guava Cache. This is configured to use a maximum size based on a percentage
> of the JVM heap size (60% by default, but configurable with startup param)
> and set a weight for objects based on their size (via ehcache sizeof or
> jamm). This should evict things before reaching the JVM limits, but we have
> seen cases where there is significant garbage collection.
> Guava cache has modes where it uses weak references or soft references for
> the values in the cache. This allows the JVM to garbage collect them if the
> system is under memory pressure. Having a configuration to enable this mode
> could avoid larger impacts if the system comes under memory pressure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
