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 "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2021/10/19 11:17:00 UTC

[jira] [Updated] (IMPALA-2424) Rack-aware scheduling

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

Csaba Ringhofer updated IMPALA-2424:
------------------------------------
    Labels: scalability scheduler  (was: scalability scheduling)

> Rack-aware scheduling
> ---------------------
>
>                 Key: IMPALA-2424
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2424
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Distributed Exec
>    Affects Versions: Impala 2.2.4
>            Reporter: Marcel Kinard
>            Priority: Minor
>              Labels: scalability, scheduler
>
> Currently, Impala makes an effort to schedule plan fragments local to the data that is being scanned; when no collocated impalad is available, the plan fragment is placed randomly.
> In order to support configurations where Impala is run on a subset of the nodes in a cluster, we should schedule fragments within the same rack that holds the assigned scan ranges (if a collocated impalad isn't available).
> See https://issues.apache.org/jira/browse/HADOOP-692 for details of how rack locality is recorded in hdfs.



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