[
https://issues.apache.org/jira/browse/HADOOP-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608579#comment-14608579
]
Kihwal Lee commented on HADOOP-12125:
-------------------------------------
What happens when the address is really bad due to misconfiguration, dns
update, etc.? Instead of retrying forever, we want it to fail after some time.
As long as there is a way to properly propagate the failure up, I am fine with
this approach. The retry proxy and the app should realize that the rpc proxy
is unusable. It should not use the same proxy to retry.
> Retrying UnknownHostException on a proxy does not actually retry hostname
> resolution
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-12125
> URL: https://issues.apache.org/jira/browse/HADOOP-12125
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Reporter: Jason Lowe
>
> When RetryInvocationHandler attempts to retry an UnknownHostException the
> hostname fails to be resolved again. The InetSocketAddress in the
> ConnectionId has cached the fact that the hostname is unresolvable, and when
> the proxy tries to setup a new Connection object with that ConnectionId it
> checks if the (cached) resolution result is unresolved and immediately throws.
> The end result is we sleep and retry for no benefit. The hostname resolution
> is never attempted again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
