Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@locus.apache.org Received: (qmail 46790 invoked from network); 26 Sep 2008 12:34:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Sep 2008 12:34:23 -0000 Received: (qmail 68164 invoked by uid 500); 26 Sep 2008 12:34:20 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 68137 invoked by uid 500); 26 Sep 2008 12:34:20 -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 68126 invoked by uid 99); 26 Sep 2008 12:34:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Sep 2008 05:34:20 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.198.233 as permitted sender) Received: from [209.85.198.233] (HELO rv-out-0506.google.com) (209.85.198.233) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Sep 2008 12:33:21 +0000 Received: by rv-out-0506.google.com with SMTP id k40so898295rvb.29 for ; Fri, 26 Sep 2008 05:33:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=6OmU/mNss7OVdSKWM8q0yCJOhNGRA1Avj+YzfUHe00Y=; b=doHekXtF6N7XU+5oKK7Rxgt7YHpRZ6qg4/YoBQHPmm4BfiYw10o+nHsB0760qilAmj /db2uzD5qKtCxffP8CAwmim7Y9BdM1VDQfR3k82e1LM1IVO585k+7+Wr/QamN0mgObxf /TgKhy3Qs1ZZfcY3/HnanONzrLtjlnlyAB+1g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=Jxh2cfGHa4Esgvioe/vSAEeH4ZK01hGxe0BW0cvssuAXswghpYXzz7H7+nasPCHpUV vLiwXfcP+aQkuT/mL5cq1bx5NOxe1qQdvgtCIpryfaleQMTENnV2GWZiEr5vhQMcUQ7K lHfTiGKaDSW+ShcsU4evY8AHoYqkxT77EoCkc= Received: by 10.142.229.5 with SMTP id b5mr557555wfh.50.1222432435667; Fri, 26 Sep 2008 05:33:55 -0700 (PDT) Received: by 10.142.101.2 with HTTP; Fri, 26 Sep 2008 05:33:55 -0700 (PDT) Message-ID: <31a243e70809260533h2721da17ib60f8a7705759cb6@mail.gmail.com> Date: Fri, 26 Sep 2008 08:33:55 -0400 From: "Jean-Daniel Cryans" Sender: jdcryans@gmail.com To: hbase-user@hadoop.apache.org Subject: Re: Load Balancing problem for HBase to host data in small size under high load In-Reply-To: <48DCD389.4050707@mails.tsinghua.edu.cn> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13660_8768687.1222432435659" References: <48DCD389.4050707@mails.tsinghua.edu.cn> X-Google-Sender-Auth: aad9976ba4cfbfbe X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_13660_8768687.1222432435659 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Zhou, The data won't be distributed until your region passes the split threshold which is by default 256MB for a single family. If you really want distribution at your level, you should lower the hbase.hregion.max.filesize value in hbase-site.xml J-D On Fri, Sep 26, 2008 at 8:20 AM, Zhou Wei wrote: > Hi, > > I've trying to use HBase 0.2.1 to host one table of data, about 200MB. > But under very high load of read and update. > I found out that all data is assigned to one data node, can't be scale > to more nodes. > > I understand that HBase is designed to store massive data. > Is there a way to balance the load to more data nodes? > > Thanks, > > Zhou > ------=_Part_13660_8768687.1222432435659--