hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8068) Do not retry rpc calls If the proxy contains unresolved address
Date Tue, 07 Apr 2015 09:19:13 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482893#comment-14482893

Steve Loughran commented on HDFS-8068:

for that reason, -1 to the current patch; all it throws is an IOE. 

# It must be an {{UnknownHostException}}
# the text should include a link to http://wiki.apache.org/hadoop/UnknownHost
# Text should also say more than "trying to create proxy", which means things to developers,
it must be something for ops & individuals. Something like "Address of namenode is not
defined, check value of <property>;  see http://wiki.apache.org/hadoop/UnknownHost"
# Test can be updated to look for the new exception

> 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

View raw message