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 "Tim Armstrong (Jira)" <ji...@apache.org> on 2019/08/22 22:00:00 UTC
[jira] [Updated] (IMPALA-7118) Add mem_limit metric listing for all
hosts in the profile
[ https://issues.apache.org/jira/browse/IMPALA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-7118:
----------------------------------
Priority: Trivial (was: Major)
> Add mem_limit metric listing for all hosts in the profile
> ---------------------------------------------------------
>
> Key: IMPALA-7118
> URL: https://issues.apache.org/jira/browse/IMPALA-7118
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.10.0, Impala 2.12.0
> Reporter: Mala Chikka Kempanna
> Priority: Trivial
> Labels: observability, ramp-up, supportability
>
> Similar to peak node memory metric in profile like below, we also need a metric listing mem_limit set on each node in profile.
> {code:java}
> Per Node Peak Memory Usage: x.y1.com:22000(36.14 GB)
> {code}
>
> Background for this ask is:
> We have seen performance issues reported post-upgrade of impala, where cluster admin would have lowered memory limits on all or subset of impala daemons while also upgrading the version.
> And query performance suffers if the queries that were running in-memory before start spilling now due to lower memory limit.
> And end-users/application-users blame the upgraded version for slowness when they share profiles for analysis, not knowing the lowering of memory limits for impala by cluster-admins was the reason.
> Having this mem limit metric in profile will help easily spot this issue.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org