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] [Updated] (HDFS-10208) Addendum for HDFS-9579: to handle the case when client machine can't resolve network path
Date Fri, 25 Mar 2016 22:47:25 GMT

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

Ming Ma updated HDFS-10208:
---------------------------
    Attachment: HDFS-10208.patch

Here is the draft patch. In the case client machine can't resolve network location, the distance
will be considered Integer.MAX_VALUE.

> 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
>         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)

Mime
View raw message