Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 78239 invoked from network); 3 Feb 2009 22:13:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Feb 2009 22:13:30 -0000 Received: (qmail 196 invoked by uid 500); 3 Feb 2009 22:13:29 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 173 invoked by uid 500); 3 Feb 2009 22:13:29 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 162 invoked by uid 99); 3 Feb 2009 22:13:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 14:13:29 -0800 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 (nike.apache.org: domain of organicveggie@gmail.com designates 74.125.44.28 as permitted sender) Received: from [74.125.44.28] (HELO yx-out-2324.google.com) (74.125.44.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 22:13:21 +0000 Received: by yx-out-2324.google.com with SMTP id 31so750386yxl.29 for ; Tue, 03 Feb 2009 14:13:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=A95aaCderfzCmb1dtmEdNis5JCkWHyUWiqpdzokTuKE=; b=q4XHFjh4AfDpcGiAOJDvcru98ptTeiFZgfEkmP8WH9b7VdDlmw42gK1NRX5p+Uvdki rHQfqw3DEwRIN+q+vkmHJXHAWm1+GIqF8NuMHR6xnPh7FLEBeyGZaMaSzBmUyK25Cdqi 841pr7FVZVRZJRMd1CM6lVdXDlcz4cJZheSHA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TDayw1d98urpS8/12jQQ8M3ZII0fJj4aO24Zjp5U0TGyI2gNqlL79N3ep9Rlj5cr+j xf+1d8yui66q5hJNGIw19WhRdsBKfecwm/qX6ZKWETfm9wDvdjQz2sjijpOzLufQsFoQ 1wsOHR0rBF2Y3GtsLBqF3L4jbjaBWFvGtJlUg= MIME-Version: 1.0 Received: by 10.151.103.2 with SMTP id f2mr2403082ybm.201.1233699180875; Tue, 03 Feb 2009 14:13:00 -0800 (PST) Date: Tue, 3 Feb 2009 16:13:00 -0600 Message-ID: Subject: HBase and Hadoop MapReduce - Common setups? From: Sean Laurent To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001517510c2c6f90d004620af920 X-Virus-Checked: Checked by ClamAV on apache.org --001517510c2c6f90d004620af920 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Howdy folks, We're evaluating HBase and we're trying to get a good solid picture of how everything fits together... specifically, we're wondering how people commonly setup HBase. I'm imagining you typically run the region servers on the same machines as the HDFS data nodes to gain data locality benefits. And from what I've seen on the mailing list, it's typically recommended (although it sounds like it's up for debate in terms of SPoF issues) to run separate machines for the HBaseMaster and NameNode servers. Is it something along the following lines? 1x HBaseMaster 1x HDFS NameNode N machines with both HRegionServer and DataNode Now what about Hadoop and task trackers? Do people typically run completely separate clusters for their M/R tasks? Do they run task trackers along side the region server and data nodes? Or add machines that run TaskTracker and DataNode servers but ~not~ HRegionServer? Any thoughts or opinions would be greatly appreciated! -Sean --001517510c2c6f90d004620af920--