[
https://issues.apache.org/jira/browse/IMPALA-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker closed IMPALA-3043.
-------------------------------
Resolution: Won't Fix
I'm not convinced this is currently not worth fixing.
> SimpleScheduler does not handle hosts with multiple IP addresses correctly
> --------------------------------------------------------------------------
>
> Key: IMPALA-3043
> URL: https://issues.apache.org/jira/browse/IMPALA-3043
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.0
> Reporter: Lars Volker
> Assignee: Lars Volker
> Priority: Minor
>
> SimpleScheduler in the backend calls HostnameToIpAddrs() to resolve a host to
> a list of its IP addresses and then picks the first non-localhost one to
> identify the host. The underlying call to getaddrinfo() might return multiple
> IP addresses to the same host in a different order on subsequent calls. The
> relevant RFC3484 only defines a partial order. A small test program confirmed
> that the order is not static. As a fix we can sort the result of
> HostnameToIpAddrs() before picking one.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
