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/10/02 17:22:00 UTC

[jira] [Updated] (IMPALA-12444) PROCESSING_COST_MIN_THREADS can get ignored by scan fragment.

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

Riza Suminto updated IMPALA-12444:
----------------------------------
    Fix Version/s: Impala 4.4.0

> PROCESSING_COST_MIN_THREADS can get ignored by scan fragment.
> -------------------------------------------------------------
>
>                 Key: IMPALA-12444
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12444
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.2.0
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> There is a bug in PlanFragment.java where scan fragment might not follow PROCESSING_COST_MIN_THREADS set by user even if total scan ranges allow to do so.
> Frontend planner also need to sanity check such that PROCESSING_COST_MIN_THREADS <= MAX_FRAGMENT_INSTANCES_PER_NODE.



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