Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82A299532 for ; Tue, 21 Feb 2012 20:09:26 +0000 (UTC) Received: (qmail 12223 invoked by uid 500); 21 Feb 2012 20:09:25 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 12150 invoked by uid 500); 21 Feb 2012 20:09:25 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 12142 invoked by uid 99); 21 Feb 2012 20:09:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 20:09:25 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.213.41 as permitted sender) Received: from [209.85.213.41] (HELO mail-yw0-f41.google.com) (209.85.213.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 20:09:19 +0000 Received: by yhoo22 with SMTP id o22so3800616yho.14 for ; Tue, 21 Feb 2012 12:08:59 -0800 (PST) Received-SPF: pass (google.com: domain of jdcryans@gmail.com designates 10.50.182.231 as permitted sender) client-ip=10.50.182.231; Authentication-Results: mr.google.com; spf=pass (google.com: domain of jdcryans@gmail.com designates 10.50.182.231 as permitted sender) smtp.mail=jdcryans@gmail.com; dkim=pass header.i=jdcryans@gmail.com Received: from mr.google.com ([10.50.182.231]) by 10.50.182.231 with SMTP id eh7mr14984018igc.29.1329854938842 (num_hops = 1); Tue, 21 Feb 2012 12:08:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=M+2NIsftRJL2/KSrBC1jBFw9dFneD+C/M0DD/qSgvQo=; b=pf5WxhIGt44lysz1dpK+3Vm8lwURHKlSLRSShX4cq96khTJTFz6Rv4gUi9V3R8QjM1 6rTcni0CeUZXEVUoFBKGLAxD6EQwOcspP8nnnr9E4QU5oAuM7eLxAasbc7F1H6mhO1rV t5jeEroL7U4LUibbRhg+Auf/dUxLEvxUnNdfg= MIME-Version: 1.0 Received: by 10.50.182.231 with SMTP id eh7mr12071620igc.29.1329854938806; Tue, 21 Feb 2012 12:08:58 -0800 (PST) Sender: jdcryans@gmail.com Received: by 10.231.3.148 with HTTP; Tue, 21 Feb 2012 12:08:58 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Feb 2012 12:08:58 -0800 X-Google-Sender-Auth: 6vAd4socNov30J4j9qfqzIFudnI Message-ID: Subject: Re: Scan performance on a big table as combination of multiple logic tables From: Jean-Daniel Cryans To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Sun, Feb 19, 2012 at 1:45 PM, Mikael Sitruk wrote: > During compaction the region is not out of service. > According to documentation the max region size for V2 format is 20G > And now the question: Assuming that 20G is the limit and the number of > regions in a single RS should stay low < 500 it means that there is no mean > having RS with more than 10TB of storage to use by HBase (otherwise > locality will not be achieve for some servers, i also assume that > compression is used and therefore it compensate the need for additional > space for replication)? > If the max number of region per RS is smaller then the storage size is even > smaller. Is it correct? In the documentation 20GB is given as an example of a larger size that can be supported, but nothing blocks you from going way higher than that. I've done some import tests and had 100GB regions. It just takes a while to compact the bigger files. Also you can go over 500 regions, in fact one of our clusters has 14,398 regions right now. It's just a pain to reassign everything when HBase boots but this is an offline cluster. J-D