hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12125) Retrying UnknownHostException on a proxy does not actually retry hostname resolution
Date Tue, 03 Nov 2015 23:28:28 GMT

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

Vinod Kumar Vavilapalli updated HADOOP-12125:
---------------------------------------------
    Target Version/s: 2.7.3  (was: 2.7.2)

Moving out all non-critical / non-blocker issues that didn't make it out of 2.7.2 into 2.7.3.
Please revert back if you disagree.

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

Mime
View raw message