[ http://issues.apache.org/jira/browse/HADOOP-685?page=comments#action_12447599 ] James Todd commented on HADOOP-685: -----------------------------------
i was thinking about a hack to get around this issue that once proven i could offer as a starting point. if someone else sees the way out on this one and has a fix in mind i do not want to be the one to hold up progress so by all means .... "make it so" > DataNode appears to require DNS name resolution as opposed to direct ip > mapping > ------------------------------------------------------------------------------- > > Key: HADOOP-685 > URL: http://issues.apache.org/jira/browse/HADOOP-685 > Project: Hadoop > Issue Type: Improvement > Components: dfs > Environment: osx, ubuntu 6.10b > Reporter: James Todd > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
