[
https://issues.apache.org/jira/browse/HADOOP-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Foley resolved HADOOP-7809.
--------------------------------
Resolution: Won't Do
Aged out.
> Backport HADOOP-5839 to 0.20-security - fixes to ec2 scripts to allow remote
> job submission
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-7809
> URL: https://issues.apache.org/jira/browse/HADOOP-7809
> Project: Hadoop Common
> Issue Type: Improvement
> Components: contrib/cloud
> Reporter: Joydeep Sen Sarma
> Priority: Major
> Attachments: ASF.LICENSE.NOT.GRANTED--hadoop-5839.2.patch
>
>
> The fix for HADOOP-5839 was committed to 0.21 more than a year ago. This bug
> is to backport the change (which is only 14 lines) to branch-0.20-security.
> ===========
> Original description:
> i would very much like the option of submitting jobs from a workstation
> outside ec2 to a hadoop cluster in ec2. This has been explored here:
> http://www.nabble.com/public-IP-for-datanode-on-EC2-tt19336240.html
> the net result of this is that we can make this work (along with using a
> socks proxy) with a couple of changes in the ec2 scripts:
> a) use public 'hostname' for fs.default.name setting (instead of the private
> hostname being used currently)
> b) mark hadoop.rpc.socket.factory.class.default as final variable in the
> generated hadoop-site.xml (that applies to server side)
> #a has no downside as far as i can tell since public hostnames resolve to
> internal/private IP addresses within ec2 (so traffic is optimally routed).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
