[
https://issues.apache.org/jira/browse/HADOOP-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590175#action_12590175
]
Tom White commented on HADOOP-2409:
-----------------------------------
bq. the ideal way to do this is by releasing hadoop for EC2 as RPMs, and have a
yum server on S3.
Is the idea that the nodes install the Hadoop RPM from S3 on startup, so you
can have a Hadoop AMI that evolves more slowly than the Hadoop release cycle?
This is similar to the patch for this issue, but using RPMs rather than
tarballs. Have you done this kind of thing before?
> 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 URL.
> 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.
