Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 35921 invoked from network); 8 Mar 2011 05:42:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Mar 2011 05:42:53 -0000 Received: (qmail 23768 invoked by uid 500); 8 Mar 2011 05:42:50 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 23579 invoked by uid 500); 8 Mar 2011 05:42:49 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 23565 invoked by uid 99); 8 Mar 2011 05:42:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 05:42:49 +0000 X-ASF-Spam-Status: No, hits=3.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mp2893@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-iw0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 05:42:41 +0000 Received: by iwr19 with SMTP id 19so6795568iwr.35 for ; Mon, 07 Mar 2011 21:42:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=sJ+SQcDa5xPMcu9AN9jBZz9/Vf3rHe+2h+WQip2UBm0=; b=VyBgrZzJy6/JfxE65uGD8+RcSViwpdA3BDY5i8EAdQ9WWQKDePE8nPrE7oil5/IB9p 2w8iuZTT7ucamXo5GsHsIki6hyuVZJefzR8OoIxubR3t7OlbOleuMXdZ0mEeetICaRh3 qPNV8ELpqk6QZM/ojVooEvZsxT0rsbRQiIaJ4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=aMx31On14wTIMAlkVguV71Xvq+dhViVvndLMGfoGm2Mm06NQ+kjJ4t7q6R7crSTknE 3lpM3LT2Kje6TREGfwFzKTcObiXvxfkxa9phKxWa7yDRqa8UZbiQlKCJLw6fCGQeFbTb Nbd+Nxr0E8V5dyBNJAHPyRQe4MIMVcyYYJpNQ= MIME-Version: 1.0 Received: by 10.231.215.42 with SMTP id hc42mr3700704ibb.1.1299562940880; Mon, 07 Mar 2011 21:42:20 -0800 (PST) Received: by 10.231.251.84 with HTTP; Mon, 7 Mar 2011 21:42:20 -0800 (PST) Date: Tue, 8 Mar 2011 14:42:20 +0900 Message-ID: Subject: Does HBase use spaces of HDFS? From: edward choi To: common-user@hadoop.apache.org, user@hbase.apache.org Content-Type: multipart/alternative; boundary=000e0cd3f18c745912049df213a6 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd3f18c745912049df213a6 Content-Type: text/plain; charset=ISO-8859-1 Sorry for this totally newbie question. I'm just wondering if HBase uses HDFS space. I read it in the reference book that HBase table size increases automatically as the table entry increases. So I am guessing that HBase manages a separate storage other than HDFS. (But then why does HBase operate on top of HDFS? Truly confusing...) If HBase doesn't use HDFS space, I can designate only a single machine to be a HDFS slave, and assign bunch of other machines to be HBase slaves. But if HBase does use HDFS space, I'd have balance the ratio of HDFS and HBase within my machines. Could anyone give me a clear heads up? Ed --000e0cd3f18c745912049df213a6--