[
https://issues.apache.org/jira/browse/HADOOP-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-4117.
-------------------------------
Resolution: Fixed
Release Note: Changed scripts to pass initialization script for EC2
instances at boot time (as EC2 user data) rather than embedding initialization
information in the EC2 image. This change makes it easy to customize the
hadoop-site.xml file for your cluster before launch, by editing the
hadoop-ec2-init-remote.sh script, or by setting the environment variable
USER_DATA_FILE in hadoop-ec2-env.sh to run a script of your choice.
Hadoop Flags: [Reviewed]
I've just committed this.
> Improve configurability of Hadoop EC2 instances
> -----------------------------------------------
>
> Key: HADOOP-4117
> URL: https://issues.apache.org/jira/browse/HADOOP-4117
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/ec2
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.19.0
>
> Attachments: hadoop-4117-v2.patch, hadoop-4117.patch
>
>
> Currently hadoop-site.xml for EC2 instances is stored as a part of the image
> and only a few properties can be controlled from the user scripts
> (compression, number of map/reduce tasks). Furthermore, it is not possible to
> rsync the configuration around the EC2 cluster with the current image, so the
> only way to customize the hadoop-site.xml file is to rebuild the image, which
> is time-consuming.
> It would be much better to pass the initialization script for nodes at boot
> time, so that it is easy to edit the configuration before starting a cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
