You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tianyi Wang (JIRA)" <ji...@apache.org> on 2018/11/19 22:11:00 UTC
[jira] [Resolved] (IMPALA-7448) Periodically evict recently unused
table from catalogd
[ https://issues.apache.org/jira/browse/IMPALA-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tianyi Wang resolved IMPALA-7448.
---------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Periodically evict recently unused table from catalogd
> ------------------------------------------------------
>
> Key: IMPALA-7448
> URL: https://issues.apache.org/jira/browse/IMPALA-7448
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 3.1.0
> Reporter: Tianyi Wang
> Assignee: Tianyi Wang
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> To limit the memory consumption of catalog, we should experiment with a mechanism automatically evicting recently unused tables from catalogd. Initial design:
> - impalad to report periodically/asynchronously the set of catalog objects that were accessed
> - catalogd to record some kind of last access time
> - catalogd to have some facility to scan over all catalog objects, collect some number of not-recently-used ones (eg to reach a target amount of evicted memory), and issue invalidate commands to itself
> - no need to have exact LRU behavior -- to simplify, we probably shouldn't try to do a classical LRU linked list between all catalog objects.
> - initial patch probably just triggered manually. Discussed either running this on a schedule or running this based on JMX GC notifications if we see that the catalogd finished an old-gen GC and the old gen is more than some target percentage full.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)