You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Igor Dvorzhak (JIRA)" <ji...@apache.org> on 2018/11/10 03:57:00 UTC

[jira] [Commented] (HADOOP-12125) Retrying UnknownHostException on a proxy does not actually retry hostname resolution

    [ https://issues.apache.org/jira/browse/HADOOP-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682187#comment-16682187 ] 

Igor Dvorzhak commented on HADOOP-12125:
----------------------------------------

[~jzhuge] May you share a patch with the fix that your colleague has?

> 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
>            Assignee: John Zhuge
>            Priority: Major
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org