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 "Bikramjeet Vig (JIRA)" <ji...@apache.org> on 2019/01/12 01:27:00 UTC
[jira] [Commented] (IMPALA-6852) Add a section to the query profile
covering number of fragments and total bytes scanned per host
[ https://issues.apache.org/jira/browse/IMPALA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740941#comment-16740941 ]
Bikramjeet Vig commented on IMPALA-6852:
----------------------------------------
[~tarmstrong] Do you think the number of *fragments instances* running per host would be a better indicator than just number of *fragments* per host?
> Add a section to the query profile covering number of fragments and total bytes scanned per host
> ------------------------------------------------------------------------------------------------
>
> Key: IMPALA-6852
> URL: https://issues.apache.org/jira/browse/IMPALA-6852
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.13.0
> Reporter: Mostafa Mokhtar
> Priority: Major
> Labels: ramp-up, supportability
>
> Root causing performance issues usually comes down to skew in terms of work done across hosts. Un-even assignment of fragments or bytes scanned per host is a common.
> Making this information readily available in the query profile will help speedup RCA.
> Proposal is to add two tables to the query profile that cover
> * Number of fragments per host
> * Number of bytes scanned per host
--
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