I abandoned HADOOP-1202 because people didn't seem to see any value in it, and I changed the way I use hadoop on ec2 around the same time. You're welcome to pick it up and port the patch to trunk; it shouldn't be too much work.
-Michael On 7/20/07 4:21 PM, "Fredrik Hedberg (JIRA)" <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/HADOOP-1638?page=com.atlassian.jira.plug > in.system.issuetabpanels:comment-tabpanel#action_12514370 ] > > Fredrik Hedberg commented on HADOOP-1638: > ----------------------------------------- > > There doesn't seem to be much action around HADOOP-1202, but it should make > this a non-issue. > >> Master node unable to bind to DNS hostname >> ------------------------------------------ >> >> Key: HADOOP-1638 >> URL: https://issues.apache.org/jira/browse/HADOOP-1638 >> Project: Hadoop >> Issue Type: Bug >> Components: contrib/ec2 >> Affects Versions: 0.13.0, 0.13.1, 0.14.0, 0.15.0 >> Reporter: Stu Hood >> Priority: Minor >> Fix For: 0.13.1, 0.14.0, 0.15.0 >> >> Attachments: hadoop-1638.patch >> >> >> With a release package of Hadoop 0.13.0 or with latest SVN, the Hadoop >> contrib/ec2 scripts fail to start Hadoop correctly. After working around >> issues HADOOP-1634 and HADOOP-1635, and setting up a DynDNS address pointing >> to the master's IP, the ec2/bin/start-hadoop script completes. >> But the cluster is unusable because the namenode and tasktracker have not >> started successfully. Looking at the namenode log on the master reveals the >> following error: >> {quote} >> 2007-07-19 16:54:53,156 ERROR org.apache.hadoop.dfs.NameNode: >> java.net.BindException: Cannot assign requested address >> at sun.nio.ch.Net.bind(Native Method) >> at >> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119) >> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) >> at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:186) >> at org.apache.hadoop.ipc.Server.<init>(Server.java:631) >> at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:325) >> at org.apache.hadoop.ipc.RPC.getServer(RPC.java:295) >> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:164) >> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:211) >> at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:803) >> at org.apache.hadoop.dfs.NameNode.main(NameNode.java:811) >> {quote} >> The master node refuses to bind to the DynDNS hostname in the generated >> hadoop-site.xml. Here is the relevant part of the generated file: >> {quote} >> <property> >> <name>fs.default.name</name> >> <value>blah-ec2.gotdns.org:50001</value> >> </property> >> <property> >> <name>mapred.job.tracker</name> >> <value>blah-ec2.gotdns.org:50002</value> >> </property> >> {quote} >> I'll attach a patch against hadoop-trunk that fixes the issue for me, but I'm >> not sure if this issue is something that someone can fix more thoroughly.
