Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30A01DCCA for ; Mon, 4 Mar 2013 15:09:14 +0000 (UTC) Received: (qmail 62058 invoked by uid 500); 4 Mar 2013 15:09:09 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 61739 invoked by uid 500); 4 Mar 2013 15:09:08 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 61723 invoked by uid 99); 4 Mar 2013 15:09:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 15:09:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cschneiderpublic@gmail.com designates 209.85.210.195 as permitted sender) Received: from [209.85.210.195] (HELO mail-ia0-f195.google.com) (209.85.210.195) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Mar 2013 15:09:02 +0000 Received: by mail-ia0-f195.google.com with SMTP id i18so1154991iac.6 for ; Mon, 04 Mar 2013 07:08:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=86xVTziuI05qQpMo9OsTra8NePOcnWTlc5QrNr12TTI=; b=deQIzxD1RlTKu2S6tgiPi+nEjNITnErWyqVe98TnrjP53DI1Q8CwH19mJhvvwQxYMF 5UQTn0el8Ppke1SiyA3QwyNhktZMMcbIcqNLoDuoVWW95Pjooix3tDt57MitP8BLXmT3 iVhCOVhhqwE5DdhZbawdjtVTnpwpgfazDtvybMzuCJiuRdcRc8CMR8ooo4c+emDSi5M+ HcZCbcL24eUBrzEd/ictm3kAInSsYODzTF7nxPdt6bEMKWF9sKlO91wXmTnhmlj7cFn2 rAVsHRjr3tHOk+vayLVGNLxUx5s/u8cTNmuys3pvu99TYBah+93Mq7C0MhBc1qlcdzrF o0aw== MIME-Version: 1.0 X-Received: by 10.50.169.6 with SMTP id aa6mr2611965igc.1.1362409721230; Mon, 04 Mar 2013 07:08:41 -0800 (PST) Received: by 10.50.111.138 with HTTP; Mon, 4 Mar 2013 07:08:41 -0800 (PST) Date: Mon, 4 Mar 2013 16:08:41 +0100 Message-ID: Subject: Best Practice: How to start and shutdown a complete cluster or adding nodes when needed (Automated with Java API or Rest) (On EC2) From: Christian Schneider To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=e89a8f2343b97991a304d71abb2b X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f2343b97991a304d71abb2b Content-Type: text/plain; charset=ISO-8859-1 Hi, what is they best way to realize this. On our current scenario we need the cluster only for some overnight processing. Therefore it would be good to shutdown the cluster overnight and store the results on s3. Could you suggest me some libraries or services for that? Like Whirr? Or is the Amazons EMR what we need (but the prices are high...)? Best Regards, Christian. --e89a8f2343b97991a304d71abb2b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
what is they best way to re= alize this.
On our current scenario we need the cluster onl= y for some overnight processing.
Therefore it would be good= to shutdown the cluster overnight and store the results on s3.

Could you suggest me some libraries or serv= ices for that? Like Whirr?
Or is the Amazons EMR what we ne= ed (but the prices are high...)?

Best = Regards,
Christian.
--e89a8f2343b97991a304d71abb2b--