[
https://issues.apache.org/jira/browse/IMPALA-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107562#comment-17107562
]
Tim Armstrong commented on IMPALA-2427:
---------------------------------------
The executor group concept added recently can solve some of these use cases.
> Utilization-aware scheduling
> ----------------------------
>
> Key: IMPALA-2427
> URL: https://issues.apache.org/jira/browse/IMPALA-2427
> Project: IMPALA
> Issue Type: Improvement
> Components: Distributed Exec
> Affects Versions: Impala 2.2.4
> Reporter: Marcel Kinard
> Priority: Minor
> Labels: admission-control, resource-management
>
> Currently, Impala tries to schedule a plan fragment local to the data it
> processes, regardless of the existing utilization of the targeted node. For
> workloads that access only a small portion of the overall HDFS blocks, this
> can lead to hot spots.
> Instead, we should take the utilization into account when making fragment
> placement decisions. The per-node utilization information can be distributed
> along with other per-node metrics that are being used for admission control.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
