[
https://issues.apache.org/jira/browse/HDFS-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated HDFS-10208:
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.0.0-alpha1
2.9.0
Status: Resolved (was: Patch Available)
Committed it to trunk and branch-2. I did notice an existing unit test failure
on branch-2, for which I filed HDFS-10415.
Thanks [~mingma] for your contribution, and [~brahmareddy] for your review!
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
