You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "bharath v (JIRA)" <ji...@apache.org> on 2019/01/30 00:07:00 UTC

[jira] [Resolved] (IMPALA-3547) Bound the size of Impalad catalog cache

     [ https://issues.apache.org/jira/browse/IMPALA-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

bharath v resolved IMPALA-3547.
-------------------------------
    Resolution: Duplicate

This is resolved via IMPALA-7127 (and its subtasks).

> Bound the size of Impalad catalog cache
> ---------------------------------------
>
>                 Key: IMPALA-3547
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3547
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>    Affects Versions: Impala 2.5.0
>            Reporter: Dimitris Tsirogiannis
>            Priority: Minor
>              Labels: catalog-server, usability
>
> Currently the catalog cache of every Impalad holds a replica of the entire catalog. In certain scenarios (e.g. large metadata), the local catalog cache is using memory that could be used more effectively elsewhere. We should consider changing the impalad catalog cache into a proper cache with a configurable size limit and an invalidation mechanism.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org