Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 49193 invoked from network); 7 Sep 2010 06:50:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Sep 2010 06:50:15 -0000 Received: (qmail 45334 invoked by uid 500); 7 Sep 2010 06:50:14 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 45009 invoked by uid 500); 7 Sep 2010 06:50:11 -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 45001 invoked by uid 99); 7 Sep 2010 06:50:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Sep 2010 06:50:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vashishtha.h@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-iw0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Sep 2010 06:50:03 +0000 Received: by iwn33 with SMTP id 33so6781962iwn.14 for ; Mon, 06 Sep 2010 23:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=uLmYiO7RwtjXA7eAD4T+m+kQsjUs8XA7aWmDleeBjRE=; b=mLo5oN4CE1Hil0PdTUik+/ut6Zw6jxqC9TJ6qv2mKO05C5mt+C15Ymr6C2QgcnoYHB elAC1VfUfXaZ2JXylA+UDsrUJFCU2r7JyeHcuv2UCd3Z/tPOQ6ELpp09ZUThOlyXwY12 x+2qMcraBJQmerAvBOfYdRpQVhPR4E4HWQJ7A= 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=bNlFGDCOfj+gqZYaFKuJR0NcS6LpKrLiQbNH/4LbTC23dWpqIc8lwOgBwS1DEr4mXU fqt0GC5T2ooyUV71p9wCazgkxvqN8nqkja1AdMSrrKe1bo2tp+RSiZEDuETWXUudwMbU I3hdb4YfBESCg3elAujKlwPBZDNw2dbNSVQDo= MIME-Version: 1.0 Received: by 10.231.36.202 with SMTP id u10mr2235408ibd.64.1283842182082; Mon, 06 Sep 2010 23:49:42 -0700 (PDT) Received: by 10.231.199.195 with HTTP; Mon, 6 Sep 2010 23:49:41 -0700 (PDT) In-Reply-To: References: <5A76F6CE309AD049AAF9A039A3924282073D5B36@sc-mbx04.TheFacebook.com> Date: Tue, 7 Sep 2010 00:49:41 -0600 Message-ID: Subject: Re: Limits on HBase From: Himanshu Vashishtha To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=0022150490db35f0ce048fa5cd51 X-Virus-Checked: Checked by ClamAV on apache.org --0022150490db35f0ce048fa5cd51 Content-Type: text/plain; charset=ISO-8859-1 Assuming you will be using hdfs as the file system: wouldn't saving those large objects in the fs and keeping a pointer to them in a hbase table serve the purpose. [I haven't done it myself but I can't see it not working. In fact, I remember reading it somewhere in the list.] ~Himanshu On Mon, Sep 6, 2010 at 11:40 PM, William Kang wrote: > Hi JG, > Thanks for your reply. As far as I have read in Hbase's documentation and > wiki, the cell size is not supposed to be larger than 10 MB. For the row, I > am not quite sure, but it looks like 256 MB is the upper limit. I am > considering store some binary data used to be stored in RDBM blob field. > The > size of those binary objects may vary from hundreds of KB to hundreds of > MB. > What would be a good way to use Hbase for it? We really want to use hbase > to > avoid that scaling problem. > Many thanks. > > > William > > On Mon, Sep 6, 2010 at 7:10 PM, Jonathan Gray wrote: > > > I'm not sure what you mean by "optimized cell size" or whether you're > just > > asking about practical limits? > > > > HBase is generally used with cells in the range of tens of bytes to > > hundreds of kilobytes. However, I have used it with cells that are > several > > megabytes, up to about 50MB. Up at that level, I have seen some weird > > performance issues. > > > > The most important thing is to be sure to tweak all of your settings. If > > you have 20MB cells, you need to be sure to increase the flush size > beyond > > 64MB and the split size beyond 256MB. You also need enough memory to > > support all this large object allocation. > > > > And of course, test test test. That's the easiest way to see if what you > > want to do will work :) > > > > When you run into problems, e-mail the list. > > > > As far as row size is concerned, the only issue is that a row can never > > span multiple regions so a given row can only be in one region and thus > be > > hosted on one server at a time. > > > > JG > > > > > -----Original Message----- > > > From: William Kang [mailto:weliam.cloud@gmail.com] > > > Sent: Monday, September 06, 2010 1:57 PM > > > To: hbase-user > > > Subject: Limits on HBase > > > > > > Hi folks, > > > I know this question may have been asked many times, but I am wondering > > > if > > > there is any update on the optimized cell size (in megabytes) and row > > > size > > > (in megabytes)? Many thanks. > > > > > > > > > William > > > --0022150490db35f0ce048fa5cd51--