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 "YifanZhang (Jira)" <ji...@apache.org> on 2023/07/25 06:09:00 UTC

[jira] [Updated] (IMPALA-12312) Support using non-default executor groups for planner

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

YifanZhang updated IMPALA-12312:
--------------------------------
    Epic Link: IMPALA-10991

> Support using non-default executor groups for planner
> -----------------------------------------------------
>
>                 Key: IMPALA-12312
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12312
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: YifanZhang
>            Priority: Minor
>
> An Impala cluster can contain multiple executor group sets, including a default executor group and non-default executor groups. The current planner always tends to pick the default executor group for scheduling a query because only the default executor group is included in the update message that is sent to the frontend.
> When we set a non-default request_pool for a query, the generated plan is still based on the default executor group, which leads to an inaccurate execution plan.
> This can be improved by sending all configured executor groups' information to the frontend.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org