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


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

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:
#<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>

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.

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

Reply via email to