Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 76498 invoked from network); 8 Mar 2011 06:26:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Mar 2011 06:26:24 -0000 Received: (qmail 34980 invoked by uid 500); 8 Mar 2011 06:26:23 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 34854 invoked by uid 500); 8 Mar 2011 06:26:22 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 34843 invoked by uid 99); 8 Mar 2011 06:26:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 06:26:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of svarma.ng@gmail.com designates 209.85.210.169 as permitted sender) Received: from [209.85.210.169] (HELO mail-iy0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 06:26:17 +0000 Received: by iyf13 with SMTP id 13so6165695iyf.14 for ; Mon, 07 Mar 2011 22:25:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=E1URkO8wM4/OPwXKSLS4JQvhoqI9XwCyLvfMD+fYyLU=; b=aL80Vnq8qSloKjJ0RwjLWNzWpJ1TGtUU02xLOSvAET5BqYqETZshXIQhtiPAJhtMT6 PqZXgYHyWVgnXyej+qZsETHVJpnjRGaZ/0a9jAOo7IvO+pp5v4koMNYZA0HxKJrv9SnP NRfYgWoh10Gl2GONJrjPJkLK4kU0yeI9LmDy4= 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 :content-type; b=t+7rND5gAESIXP2oFcXrlJAf9jiJqmWVzQQO2x34d1y1B73i9XL4g8nslcwwywGOmd KqoKiAtIzD+fzt7w0QhS5VeltNEH7UvxHi1SgbnxCZzbTnHZWsy5gtUDES09yR280TjG SySeIdOWRAHxZRBYcJ50ib9BgDO00wgE/QQ4E= MIME-Version: 1.0 Received: by 10.42.150.132 with SMTP id a4mr6133181icw.199.1299565556335; Mon, 07 Mar 2011 22:25:56 -0800 (PST) Received: by 10.231.206.148 with HTTP; Mon, 7 Mar 2011 22:25:56 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Mar 2011 22:25:56 -0800 Message-ID: Subject: Re: Does HBase use spaces of HDFS? From: Suraj Varma To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=90e6ba212373590350049df2af5a --90e6ba212373590350049df2af5a Content-Type: text/plain; charset=ISO-8859-1 In the standalone mode, HBase uses the local file system as its storage. In pseudo-distributed and fully-distributed modes, HBase uses HDFS as the storage. See http://hbase.apache.org/notsoquick.html for more details on the different modes. For details on storage, see http://www.larsgeorge.com/2009/10/hbase-architecture-101-storage.html --Suraj On Mon, Mar 7, 2011 at 9:42 PM, edward choi wrote: > 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 > --90e6ba212373590350049df2af5a--