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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/11/26 18:55:00 UTC

[jira] [Updated] (IMPALA-7541) Avoid instantiating metrics for IncompleteTables

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

Todd Lipcon updated IMPALA-7541:
--------------------------------
    Priority: Critical  (was: Major)

Bumping priority for this since I think this will cause big problems on upgrade for users who have a high number of tables

> Avoid instantiating metrics for IncompleteTables
> ------------------------------------------------
>
>                 Key: IMPALA-7541
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7541
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Todd Lipcon
>            Priority: Critical
>
> Currently we instantiate a Metrics object for every table. However in many cases, users have hundreds of thousands or millions of tables and only a small subset are loaded. This is even more likely after the new automatic invalidation work in progress. So, we should try to minimize memory footprint of IncompleteTable. The largest culprit there seems to be the new Metrics object added by IMPALA-4886. We should lazily init this only on *loaded* tables.



--
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