You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ming Ma (JIRA)" <ji...@apache.org> on 2016/03/25 23:47:25 UTC

[jira] [Updated] (HDFS-10208) Addendum for HDFS-9579: to handle the case when client machine can't resolve network path

     [ https://issues.apache.org/jira/browse/HDFS-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ming Ma updated HDFS-10208:
---------------------------
    Assignee: Ming Ma
      Status: Patch Available  (was: Open)

> 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
>         Attachments: HDFS-10208.patch
>
>
> If DFSClient runs on a machine that can't resolve network path, e.g.{{dnsToSwitchMapping.resolve}} returns null, that will cause exception when it tries to create {{clientNode}}. In such case, there is no need to create {{clientNode}} as null {{clientNode}} means its network distance with any datanode is Integer.MAX_VALUE, which is what we want.
> {noformat}
>     clientNode = new NodeBase(clientHostName,
>         dnsToSwitchMapping.resolve(nodes).get(0));
> {noformat}



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