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 "Riza Suminto (Jira)" <ji...@apache.org> on 2023/04/11 12:40:00 UTC

[jira] [Updated] (IMPALA-12032) PROCESSING_COST_MIN_THREADS fail to cap minimum parallelism

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

Riza Suminto updated IMPALA-12032:
----------------------------------
        Fix Version/s: Impala 4.3.0
                           (was: Impala 4.2.0)
    Affects Version/s: Impala 4.3.0
                           (was: Impala 4.2.0)

> PROCESSING_COST_MIN_THREADS fail to cap minimum parallelism
> -----------------------------------------------------------
>
>                 Key: IMPALA-12032
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12032
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.3.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 4.3.0
>
>
> PROCESSING_COST_MIN_THREADS suppose to be a lower bound of per node parallelism when CPU costing algorithm adjust fragment parallelism across executor group set. But PlanFragment.adjustToMaxParallelism() does not take account of it during adjustment.



--
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