[
https://issues.apache.org/jira/browse/IMPALA-12005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riza Suminto resolved IMPALA-12005.
-----------------------------------
Fix Version/s: Impala 4.3.0
Resolution: Fixed
The fix has been merged.
> 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
> Assignee: Riza Suminto
> Priority: Critical
> Fix For: Impala 4.3.0
>
>
> [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)
