hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10208) Addendum for HDFS-9579: to handle the case when client machine can't resolve network path
Date Tue, 17 May 2016 02:05:12 GMT

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

Ming Ma commented on HDFS-10208:
--------------------------------

Thank you [~sjlee0] and [~brahmareddy]!

> Addendum for HDFS-9579: to handle the case when client machine can't resolve network
path
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-10208
>                 URL: https://issues.apache.org/jira/browse/HDFS-10208
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>             Fix For: 2.9.0, 3.0.0-alpha1
>
>         Attachments: HDFS-10208-2.patch, HDFS-10208-3.patch, HDFS-10208-4.patch, HDFS-10208-5.patch,
HDFS-10208.patch
>
>
> If DFSClient runs on a machine that can't resolve network path, {{DNSToSwitchMapping}}
will return {{DEFAULT_RACK}}. In addition, if somehow {{dnsToSwitchMapping.resolve}} returns
null, that will cause exception when it tries to create {{clientNode}}. In either case, there
is no need to create {{clientNode}} and we should treat its network distance with any datanode
as Integer.MAX_VALUE.
> {noformat}
>     clientNode = new NodeBase(clientHostName,
>         dnsToSwitchMapping.resolve(nodes).get(0));
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message