You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Matt Foley (Updated) (JIRA)" <ji...@apache.org> on 2011/11/09 02:41:51 UTC
[jira] [Updated] (HADOOP-7809) Backport HADOOP-5839 to
0.20-security - fixes to ec2 scripts to allow remote job submission
[ https://issues.apache.org/jira/browse/HADOOP-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Foley updated HADOOP-7809:
-------------------------------
Description:
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).
was:
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).
Target Version/s: 0.20.205.1
Fix Version/s: (was: 0.21.0)
Assignee: Matt Foley (was: Joydeep Sen Sarma)
Hadoop Flags: (was: Reviewed)
> 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
> Assignee: Matt Foley
> Attachments: 5839.1.patch, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira