hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5839) fixes to ec2 scripts to allow remote job submission
Date Thu, 21 May 2009 14:32:45 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tom White updated HADOOP-5839:

       Resolution: Fixed
    Fix Version/s: 0.21.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)


I've just committed this. Thanks Joydeep!

> fixes to ec2 scripts to allow remote job submission
> ---------------------------------------------------
>                 Key: HADOOP-5839
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5839
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/ec2
>            Reporter: Joydeep Sen Sarma
>            Assignee: Joydeep Sen Sarma
>             Fix For: 0.21.0
>         Attachments: 5839.1.patch, hadoop-5839.2.patch
> 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.
You can reply to this email to add a comment to the issue online.

View raw message