[
https://issues.apache.org/jira/browse/IMPALA-11979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-11979.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Support option for consistent scan range scheduling across executor
> invocations with changing IP address
> --------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-11979
> URL: https://issues.apache.org/jira/browse/IMPALA-11979
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 4.2.0
> Reporter: David Rorke
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> The scheduler currently assigns scan ranges to executor hosts using a hash
> ring with the executor IP used as the hash key. This results in varying scan
> range assignments across multiple instantiations of an executor if the
> executor IP changes. This makes it more difficult to get repeatable
> scheduling behavior when debugging or performance testing in an environment
> where executor IPs can be assigned dynamically.
> We should support a mode where the scheduler's executor hashing uses a fixed
> executor identifier that we specify (unique within an executor group). This
> could also be useful for potential future optimizations like cache prewarming
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
