hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris K Wensel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2409) Make EC2 image independent of Hadoop version
Date Wed, 27 Feb 2008 15:37:51 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572939#action_12572939

Chris K Wensel commented on HADOOP-2409:

I think supporting both modes would be optimal. 

having apps install on the fly during boot adds one more failure mode when dealing with reasonably
large clusters. there is already no guarantee a ec2 instance will boot, having one hang up
during config adds for one more thing to debug. 

that said, i would worry about this for 'production' instances, and not instances i'm testing
with. thus having apps install on the fly would help as scripts and configuration issues are
ironed out.

if i had to chose one, since having both is a lot to ask for, i would chose a static install.
but I could live with either.

> Make EC2 image independent of Hadoop version
> --------------------------------------------
>                 Key: HADOOP-2409
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2409
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/ec2
>            Reporter: Tom White
>         Attachments: HADOOP-2409.patch
> Instead of building a new image for each released version of Hadoop, install Hadoop on
instance start up. Since it is a small download this would not add significantly to startup
time. Hadoop releases would be mirrored on S3 for scalability (and to avoid bandwidth costs).
The version to install would be found from the instance metadata - this would be a download
> More generally, the instance could retrieve a script to run on start up from a URL specified
in the metadata. The script would install and configure Hadoop, but it could be extended to
do cluster-specific set up.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message