[
https://issues.apache.org/jira/browse/HADOOP-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465849
]
James P. White commented on HADOOP-884:
---------------------------------------
I'm quite sure the solution to the DNS problem is Zeroconf.
http://www.ifcx.org/wiki/LocalNetworking.html
http://zeroconf.org/
Amazon is already using it for the parameterized launch. That where the funny
"169.254.169.254" address comes from.
http://docs.amazonwebservices.com/AmazonEC2/dg/2006-10-01/TechnicalFAQ.html#d0e14061
There are several ways that this can be approached. The one that would help
the most people would be to make Hadoop Zeroconf-aware (slaves using service
discovery to find the master), but probably the place to start is to just
enhance these EC2 scripts.
> Create scripts to run Hadoop on Amazon EC2
> ------------------------------------------
>
> Key: HADOOP-884
> URL: https://issues.apache.org/jira/browse/HADOOP-884
> Project: Hadoop
> Issue Type: New Feature
> Components: scripts
> Affects Versions: 0.10.1
> Reporter: Tom White
> Assigned To: Tom White
> Attachments: hadoop-ec2-v1.tar.gz
>
>
> It is already possible to run Hadoop on Amazon EC2
> (http://wiki.apache.org/lucene-hadoop/AmazonEC2), however it is a rather
> involved, largely manual process. By writing scripts to automate (as far as
> is possible) image creation and cluster launch it will make it much easier to
> use Hadoop on EC2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
