Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
Impala 2.2.4
-
None
Description
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.
Attachments
Issue Links
- relates to
-
IMPALA-6088 Rack aware broadcast operator
- Open