[
https://issues.apache.org/jira/browse/IMPALA-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112478#comment-18112478
]
Quanlong Huang commented on IMPALA-13449:
-----------------------------------------
One reason this work is delayed for a while is we keep improving the Iceberg
metadata memroy usage. So the estimation also need evolving.
To get the magic numbers for estimating memory usage, we can perform a heap
dump analysis after catalogd loads a large table. Here is the wiki:
[https://cwiki.apache.org/confluence/spaces/IMPALA/pages/327977753/Impala+JVM+Heap+Dump+Analysis]
We can get how large a FileDescriptor is and how large an IcebergTable is, etc.
There is an example in IMPALA-13117.
> Improve / Correct the Table Size in Catalog Web UI for External and Iceberg
> Tables
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-13449
> URL: https://issues.apache.org/jira/browse/IMPALA-13449
> Project: IMPALA
> Issue Type: New Feature
> Components: Catalog
> Reporter: Manish Maheshwari
> Assignee: Arnab Karmakar
> Priority: Critical
>
> Improve / Correct the Table Size in Catalog Web UI for External and Iceberg
> Tables. The current size shows tables extremely small and the logic needs to
> be refreshed for Iceberg tables
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
