You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2023/09/26 05:37:00 UTC
[jira] [Resolved] (IMPALA-8675) Remove db/table count metrics from impalad in LocalCatalog mode
[ https://issues.apache.org/jira/browse/IMPALA-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Quanlong Huang resolved IMPALA-8675.
------------------------------------
Fix Version/s: Impala 4.4.0
Resolution: Fixed
[~MikaelSmith] If we still have chance, it'd be nice to have this fix in 4.3.0.
> Remove db/table count metrics from impalad in LocalCatalog mode
> ---------------------------------------------------------------
>
> Key: IMPALA-8675
> URL: https://issues.apache.org/jira/browse/IMPALA-8675
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Reporter: Todd Lipcon
> Assignee: Quanlong Huang
> Priority: Minor
> Labels: catalog-v2
> Fix For: Impala 4.4.0
>
>
> In LocalCatalog there is no need for every coordinator to have the full list of tables of every database. But, getCatalogMetrics ends up iterating over every DB and fetching these lists in order to provide a count. The count isn't particularly relevant -- if someone wants to keep track of the size of their catalog they are better off looking at that metric from catalogd. We should remove these catalog metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)