Thanks Philip. Very helpful (and great blog post)! This seems to make basic dfs command line operations work just fine.
However - I am hitting a new error during job submission (running hadoop-0.19.0):
2009-05-14 00:15:34,430 ERROR exec.ExecDriver (SessionState.java:printError(279)) - Job Submission failed with exception 'java.net.UnknownHostException(unknown host: domU-12-31-39-00-51-94.compute-1.internal)'
java.net.UnknownHostException: unknown host: domU-12-31-39-00-51-94.compute-1.internal
at $Proxy0.getProtocolVersion(Unknown Source)
looking at the stack trace and the code - it seems that this is happening because the jobclient asks for the mapred system directory from the jobtracker - which replies back with a path name that's qualified against the fs.default.name setting of the jobtracker. Unfortunately the standard EC2 scripts assign this to the internal hostname of the hadoop master.
Is there any downside to using public hostnames instead of the private ones in the ec2 starter scripts?
Thanks for the help,
From: Philip Zeyliger [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 13, 2009 2:40 PM
To: [EMAIL PROTECTED]
Subject: Re: public IP for datanode on EC2
On Tue, May 12, 2009 at 9:11 PM, Joydeep Sen Sarma <[EMAIL PROTECTED]> wrote:
> (raking up real old thread)
> After struggling with this issue for sometime now - it seems that accessing hdfs on ec2 from outside ec2 is not possible.
> This is primarily because of https://issues.apache.org/jira/browse/HADOOP-985. Even if datanode ports are authorized in ec2 and we set the public hostname via slave.host.name - the namenode uses the internal IP address of the datanodes for block locations. DFS clients outside ec2 cannot reach these addresses and report failure reading/writing data blocks.
> HDFS/EC2 gurus - would it be reasonable to ask for an option to not use IP addresses (and use datanode host names as pre-985)?
> I really like the idea of being able to use an external node (my personal workstation) to do job submission (which typically requires interacting with HDFS in order to push files into the jobcache etc). This way I don't need custom AMIs - I can use stock hadoop amis (all the custom software is on the external node). Without the above option - this is not possible currently.
You could use ssh to set up a SOCKS proxy between your machine and
ec2, and setup org.apache.hadoop.net.SocksSocketFactory to be the
has more information.