Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 94650 invoked from network); 28 Mar 2009 06:08:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Mar 2009 06:08:46 -0000 Received: (qmail 22979 invoked by uid 500); 28 Mar 2009 06:08:44 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 22878 invoked by uid 500); 28 Mar 2009 06:08:44 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Delivered-To: moderator for core-user@hadoop.apache.org Received: (qmail 19706 invoked by uid 99); 28 Mar 2009 05:44:04 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of arber.research@gmail.com designates 209.85.198.235 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=nC/ETHsEqliv4JZQqzGE2l5Qyp1y+d2nIb7F48HM1pg=; b=QkNclu4a4MFfnDe7lkYVjb6YbzxY2n3RFdgFx0YZaO3geW6IHW46S02+X1HxMGg/jC F1JhamhzRN2hizXiPOXA97XDLz9/gHZOEK5GKi6Kd61Z+R6QTeS42g0bgzICnsO9Arv3 MIm6lAVqhjF5nia/eC9quNouMRPRe+u5/bcSw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rls1h0O47lxwybfaoF3WGl4yvJ+5Ip5spnJrf4C0W1mbW0BZNMTulRWLjrhGiDmEU0 vpIgZ77aMCLOmTWaI/xxZuE50J8j639iO53Ud/eqqJdfIBOqBXyKS4YNT+TJ5g5SUrV6 HkDRCzXUcYnbROyyH1t3nTOGk0TYU793ExKfo= MIME-Version: 1.0 In-Reply-To: <35a22e220903272207s30f26310y3ecbec723b83e229@mail.gmail.com> References: <35a22e220903272207s30f26310y3ecbec723b83e229@mail.gmail.com> Date: Fri, 27 Mar 2009 22:43:37 -0700 Message-ID: <382e1efc0903272243v2952aa6cgf92045e57b09ee45@mail.gmail.com> Subject: Re: Typical hardware configurations From: Yabo-Arber Xu To: hbase-user@hadoop.apache.org Cc: core-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd2e61cac21d104662754bd X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd2e61cac21d104662754bd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Amandeep, I just did the same investigation not long ago, and I was recommended to get Amazon EC2 X-Large equivalentnodes: , 8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each), 15 GB memory, 1690 GB of instance storage, 64-bit platform. One EC2 Compute Unit (ECU) is equivalent to CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor. For more details, you may want to refer to Daniel Leffel's experience on setting up HBase Hope it helps. Best, Arber On Fri, Mar 27, 2009 at 10:07 PM, Amandeep Khurana wrote: > What are the typical hardware config for a node that people are using for > Hadoop and HBase? I am setting up a new 10 node cluster which will have > HBase running as well that will be feeding my front end directly. > Currently, > I had a 3 node cluster with 2 GB of RAM on the slaves and 4 GB of RAM on > the > master. This didnt work very well due to the RAM being a little low. > > I got some config details from the powered by page on the Hadoop wiki, but > nothing like that for Hbase. > > > Amandeep Khurana > Computer Science Graduate Student > University of California, Santa Cruz > --000e0cd2e61cac21d104662754bd--