Resolved: (HADOOP-685) DataNode appears to require DNS name resolution as opposed to direct ip mapping

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Resolved: (HADOOP-685) DataNode appears to require DNS name resolution as opposed to direct ip mapping

Hudson (Jira)

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

Raghu Angadi resolved HADOOP-685.
---------------------------------

    Resolution: Duplicate

> DataNode appears to require DNS name resolution as opposed to direct ip mapping
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-685
>                 URL: https://issues.apache.org/jira/browse/HADOOP-685
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>         Environment: osx, ubuntu 6.10b
>            Reporter: James Todd
>         Assigned To: Raghu Angadi
>            Priority: Minor
>
> DataNode appears to require DNS resolution of nodes via the class org.apache.hadoop.net.DNS as opposed being able to use a specified ip.
> as an example, i was not able to set up more then one instance of dfs datanodes on one box using loopback w/ varying ports since DataNode
> resolved the ip of 127.0.0.1 to be "foo.bar" which was then mapped to the dhcp allocated ip of 192.168.0.***, which was not addressable by the
> rest of the dfs cluster (namely namenode).
> while this example is trivial one should be able to use the very same process yet change only the ip's of the nodes and have things work as
> expected.
> it would be nice to not always require nds resolution.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.