[jira] [Commented] (IMPALA-9687) Plans for Kudu can contains hosts > num of Impala nodes

["Tim Armstrong (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091032#comment-17091032 ] 

Tim Armstrong commented on IMPALA-9687:
---------------------------------------

The (way more complex) logic for HdfsScanNode handles this by determining which executors actually have local scan ranges. It also caps the estimate at # executors.
https://github.com/apache/impala/blob/0167c5b4242fcebf6be19aba5ecfb440204278ad/fe/src/main/java/org/apache/impala/planner/HdfsScanNode.java#L1238

The basic fix is to cap it at # of executors. The more complex fix would be to intersect the list of locations with impala execution.
https://github.com/apache/impala/blob/0167c5b4242fcebf6be19aba5ecfb440204278ad/fe/src/main/java/org/apache/impala/planner/KuduScanNode.java#L281

> Plans for Kudu can contains hosts > num of Impala nodes
> -------------------------------------------------------
>
>                 Key: IMPALA-9687
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9687
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>            Reporter: Csaba Ringhofer
>            Priority: Major
>              Labels: kudu, ramp-up
>
> Started a cluster with 1 coordinator and 1 executor:
> {code}
> bin/start-impala-cluster.py -c 1 --use_exclusive_coordinator -s 2
> {code}
> Queries on Kudu tables still contained hosts=3, while all other table types had hosts=1.
> {code}
> explain select * from functional_kudu.alltypestiny;
> Result:
> ...
> F00:PLAN FRAGMENT [RANDOM] hosts=3 instances=3
> ...
> {code}
> The numbers in the plan are only estimates, the summary after the query contained 1 host.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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