[
https://issues.apache.org/jira/browse/HDFS-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484238#comment-14484238
]
Kihwal Lee commented on HDFS-8068:
----------------------------------
bq. could you include the entire error text in the exception that is thrown,
as well as the logs. It's most likely to get seen then.
It is possible to pass any string to {{UnknownHostException}}, but it is meant
for the host name. If you insist, I will make it pass the entire error string.
bq. the test can be changed to catch a UnknownHostException, removing the
need to look inside its string value. this makes for a more robust test
The failover proxy provider catches it and throws a RunTimeException. I think
this is to bypass the checks {{shouldRetry()}} in retry policies and make the
exception bubble up.
> 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, HDFS-8068.v2.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)
