Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 6158 invoked from network); 28 Aug 2010 20:06:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Aug 2010 20:06:38 -0000 Received: (qmail 85943 invoked by uid 500); 28 Aug 2010 20:06:37 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 85896 invoked by uid 500); 28 Aug 2010 20:06:37 -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 85888 invoked by uid 99); 28 Aug 2010 20:06:37 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Aug 2010 20:06:37 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,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 ryanobjc@gmail.com designates 74.125.82.41 as permitted sender) Received: from [74.125.82.41] (HELO mail-ww0-f41.google.com) (74.125.82.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Aug 2010 20:06:15 +0000 Received: by wwb31 with SMTP id 31so2660427wwb.2 for ; Sat, 28 Aug 2010 13:05:55 -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 :content-transfer-encoding; bh=vT+8U9MzQ4RzHU3Cn/HaZEqllYFuTpKYsoI0dwj82Ng=; b=iXY79Ne2o63+uilvqlHPKqHPOwgaFAeirPKFpX0JxOzDbEdO45j5HreRE78JBwUnQ5 wGdrUJorBLsfSAiJdkES1OHTp4HAdMhTJAfmQgKI0mktuOQaNJtj4/H26ej4pfPE9uds wfEPgTeyaxKIoWYhZEGlJ3atk60isPMnhyKeI= 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:content-transfer-encoding; b=cNXMVHPEXtRrRSRntNNTZNovxRBWWaDK2ry9Zk0SIv3LzcfMu4jpzJwJDCD/bwrU0x eoZilBaCFTqhVLTFveIKUdPqwSXxCirXBBP1RvCpK5fMY/dSs7Oa3xLk9LOWYQfSczC8 jZZhg2t1dCRzJp1T3TxXzz8QWudpLZsAr2xzY= MIME-Version: 1.0 Received: by 10.216.26.194 with SMTP id c44mr2646132wea.104.1283025955348; Sat, 28 Aug 2010 13:05:55 -0700 (PDT) Received: by 10.216.160.71 with HTTP; Sat, 28 Aug 2010 13:05:55 -0700 (PDT) In-Reply-To: <5A76F6CE309AD049AAF9A039A39242820732D148@sc-mbx03.TheFacebook.com> References: <2D6136772A13B84E95DF6DA79E85A9F0011D292DD208@NSPEXMBX-A.the-lab.llnl.gov> <5A76F6CE309AD049AAF9A039A39242820732D148@sc-mbx03.TheFacebook.com> Date: Sat, 28 Aug 2010 13:05:55 -0700 Message-ID: Subject: Re: how many regions a regionserver can support From: Ryan Rawson To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org The only downside to having so many regions on a regionserver is opening and reassigning them is not as fast as you'd like. In the future with increased parallelism and other things we will be able to speed it up. On Fri, Aug 27, 2010 at 10:55 AM, Jonathan Gray wrote: > There is no fixed limit, it has much more to do with the read/write load = than the actual dataset size. > > HBase is usually fine having very densely packed RegionServers, if much o= f the data is rarely accessed. =A0If you have extremely high numbers of reg= ions per server and you are writing to all of these regions, or even readin= g from all of them, you could have issues. =A0Though storage capacity needs= to be considered, capacity planning often has much more to do with how muc= h memory you need to support the read/write load you expect. =A0Reads mostl= y from a performance POV but for writes, there are some important considera= tions related to the number of regions per server (and thus data density an= d determining your max region size). > > In any case, you should probably increase your max size to 1GB or so and = can go higher if necessary. > > JG > >> -----Original Message----- >> From: Jinsong Hu [mailto:jinsong_hu@hotmail.com] >> Sent: Friday, August 27, 2010 10:03 AM >> To: user@hbase.apache.org >> Subject: how many regions a regionserver can support >> >> Hi, There : >> =A0 =A0Does anybody know how many region a regionserver can support ? I >> have >> regionservers with 8G ram and 1.5T disk and 4 core CPU. >> I searched http://www.facebook.com/note.php?note_id=3D142473677002 and >> they >> say google target is 100 regions of 200M for each >> regionserver. >> =A0 In my case, I have 2700 regions spread to 6 regionservers. each >> region is >> set to default size of 256M . and it seems it is still running fine. I >> am >> running CDH3. =A0I just wonder what is the upper limit so that I can do >> capacity planning. Does anybody know this ? >> >> Jimmy. > >