[
https://issues.apache.org/jira/browse/HDFS-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483426#comment-14483426
]
Kihwal Lee commented on HDFS-8068:
----------------------------------
Thanks for the review, [[email protected]]
The updated patch throws an {{UnknownHostException}} and shows the following
log message:
{panel}
2015-04-07 10:59:45,068 ERROR hdfs.NameNodeProxies
(NameNodeProxies.java:createNonHAProxy(314)) - The specified namenode name
could not be resolved: this.doesnt.exist. See
http://wiki.apache.org/hadoop/UnknownHost for possible causes.
{panel}
> Do not retry rpc calls If the proxy contains unresolved address
> ---------------------------------------------------------------
>
> Key: HDFS-8068
> URL: https://issues.apache.org/jira/browse/HDFS-8068
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: HDFS-8068.v1.patch
>
>
> When the InetSocketAddress object happens to be unresolvable (e.g. due to
> transient DNS issue), the rpc proxy object will not be usable since the
> client will throw UnknownHostException when a Connection object is created.
> If FailoverOnNetworkExceptionRetry is used as in the standard HA failover
> proxy, the call will be retried, but this will never recover. Instead, the
> validity of address must be checked on pxoy creation and throw if it is
> invalid.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
