You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Sailesh Mukil (JIRA)" <ji...@apache.org> on 2018/06/19 21:23:00 UTC

[jira] [Resolved] (IMPALA-4970) Record identity of largest latency ExecQueryFInstances() RPC per query

     [ https://issues.apache.org/jira/browse/IMPALA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sailesh Mukil resolved IMPALA-4970.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

> Record identity of largest latency ExecQueryFInstances() RPC per query
> ----------------------------------------------------------------------
>
>                 Key: IMPALA-4970
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4970
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Distributed Exec
>    Affects Versions: Impala 2.9.0
>            Reporter: Henry Robinson
>            Assignee: Rahul Shivu Mahadev
>            Priority: Major
>              Labels: newbie, ramp-up
>             Fix For: Impala 3.1.0
>
>
> Although we retain the histogram of fragment instance startup latencies, we don't record the identity of the most expensive instance, or the host it runs on. This would be helpful in diagnosing slow query start-up times.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)