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 "Dinesh Garg (JIRA)" <ji...@apache.org> on 2018/11/02 22:32:00 UTC
[jira] [Resolved] (IMPALA-4870) Extend Catalog metrics
[ https://issues.apache.org/jira/browse/IMPALA-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Garg resolved IMPALA-4870.
---------------------------------
Resolution: Won't Fix
Triaging notes : Memory management will take care of adding metrics here. Closing this.
> Extend Catalog metrics
> ----------------------
>
> Key: IMPALA-4870
> URL: https://issues.apache.org/jira/browse/IMPALA-4870
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 2.6.0
> Reporter: Mostafa Mokhtar
> Priority: Major
> Labels: catalog-server, supportability
>
> It is difficult to tune and debug the Catalog performance as it doesn't expose any metrics indicating the current state.
> The Catalog should expose object count and estimate memory consumed by each object type
> * Partitions
> * Files
> * Blocks
> A breakdown per DB/Table/Partition would be ideal.
> Also a measure of heap usage by the JVM along with GC time as a % of the JVM lifetime.
--
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