You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2023/03/15 19:58:00 UTC

[jira] [Created] (IMPALA-12005) Explain executor group set selection criteria in query profile

Riza Suminto created IMPALA-12005:
-------------------------------------

             Summary: Explain executor group set selection criteria in query profile
                 Key: IMPALA-12005
                 URL: https://issues.apache.org/jira/browse/IMPALA-12005
             Project: IMPALA
          Issue Type: Improvement
          Components: Frontend
    Affects Versions: Impala 4.2.0
            Reporter: Riza Suminto


[IMPALA-10992|http://issues.cloudera.org/browse/IMPALA-10992] and [IMPALA-11604|http://issues.cloudera.org/browse/IMPALA-11604]  adds memory and cpu constraint criteria for executor group set selection. We should explain this selection criteria in query profile. Things that we should consider adding to query profile:
 * The effective degree of parallelism (EDoP) value that was used to calculate fitness for a given group. Possibly some additional details about how we got to that EDoP like the per fragment values.

 * Per host memory estimate for that group.
 * Reason for not choosing a given group (if any) - was it based on memory or CPU, what thresholds were we comparing to, etc.

In the event of none executor group set is fit, the returned AnalysisException also need to provide more context. Right now, only these are returned:
{code:java}
AnalysisException: The query does not fit any executor group sets. {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)