Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 64864 invoked from network); 17 Sep 2008 20:30:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Sep 2008 20:30:09 -0000 Received: (qmail 42415 invoked by uid 500); 17 Sep 2008 20:30:03 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 42391 invoked by uid 500); 17 Sep 2008 20:30:03 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 42380 invoked by uid 99); 17 Sep 2008 20:30:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2008 13:30:03 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2008 20:29:13 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 36E1E234C1D6 for ; Wed, 17 Sep 2008 13:29:44 -0700 (PDT) Message-ID: <91709130.1221683384212.JavaMail.jira@brutus> Date: Wed, 17 Sep 2008 13:29:44 -0700 (PDT) From: "Tom White (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-4117) Improve configurability of Hadoop EC2 instances In-Reply-To: <1717828708.1220894024309.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated HADOOP-4117: ------------------------------ Attachment: hadoop-4117-v2.patch I did a local chmod and it worked - I've used these scripts a few times. But here's a new patch where the file's mode is changed on the instance, which should be more reliable (although scp -p would be an alternative). > 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.