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 "Balazs Jeszenszky (JIRA)" <ji...@apache.org> on 2018/08/22 10:57:00 UTC

[jira] [Commented] (IMPALA-7474) Tool to identify CPU bottlenecks

    [ https://issues.apache.org/jira/browse/IMPALA-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588701#comment-16588701 ] 

Balazs Jeszenszky commented on IMPALA-7474:
-------------------------------------------

[~anujphadke] where would these 'calls' be printed? Profiles, logs, some new place? What is the expected output of seeing these calls, e.g. how would the output look like in the common but hard to identify case of concurrent queries competing for CPU?

> Tool to identify CPU bottlenecks
> --------------------------------
>
>                 Key: IMPALA-7474
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7474
>             Project: IMPALA
>          Issue Type: Improvement
>    Affects Versions: Impala 2.12.0
>            Reporter: Anuj Phadke
>            Assignee: Anuj Phadke
>            Priority: Major
>              Labels: supportability
>
> We run into a bunch of issues where we run impala into hangs or impacts query performance issues due to a very high CPU usage.
> A tool which periodically collects stacks from impala (when enabled) and prints calls with high CPU usage would be very useful for debugging such issues. 
> Running this tool should ideally incur a minimalistic overhead on impalad while collecting the stacks.



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