Joe McDonnell created IMPALA-14725:
--------------------------------------
Summary: Consider calling cleanUp() periodically for the Guava
Cache in CatalogdMetaProvider
Key: IMPALA-14725
URL: https://issues.apache.org/jira/browse/IMPALA-14725
Project: IMPALA
Issue Type: Task
Components: Catalog
Affects Versions: Impala 5.0.0
Reporter: Joe McDonnell
CatalogdMetaProvider caches metadata using a Guava cache. This is configured
with a maximum size and an expiration time. Guava documentation says:
{noformat}
Caches built with CacheBuilder do not perform cleanup and evict values
"automatically," or instantly after a value expires, or anything of the sort.
Instead, it performs small amounts of maintenance during write operations, or
during occasional read operations if writes are rare.{noformat}
https://github.com/google/guava/wiki/cachesexplained#when-does-cleanup-happen
We have the option of running Cache.cleanUp() periodically to force it to do
maintenance even if the system is idle. This may make time-based expiration
more consistent for lightly loaded systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
