Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7BA4D10F68 for ; Tue, 3 Dec 2013 19:47:23 +0000 (UTC) Received: (qmail 45672 invoked by uid 500); 3 Dec 2013 19:47:21 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 45612 invoked by uid 500); 3 Dec 2013 19:47:21 -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 45604 invoked by uid 99); 3 Dec 2013 19:47:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2013 19:47:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kevin.odell@cloudera.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qc0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2013 19:47:16 +0000 Received: by mail-qc0-f180.google.com with SMTP id w7so2541132qcr.11 for ; Tue, 03 Dec 2013 11:46:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=wHMphqSp7ehbOOu1xuvwdEpFJ6THbYWPpGPilU7yshg=; b=QS5NUe8Px8y8JGoj6bSxOCeELfFR2YXgruec8po2qMN3SOeo7kVaceu0oZr9ToUMYh z/HQKAneFgCIvIIjsQj/zlDhFxZeqXW/WPTIRhBJIh82v6MZcD3JWO9Abc5IPQ+p8l9/ IKxCcHbimCBkdBDEv7srZMqWbbX4kmW3Njk2gH/+K8ZfI3DCRnkIpJeV094RZw0eYskI bQzXUKOhjbluq5KthyS+WyC+szGAjm3lkZ925rnVPuEMZmHwtnURmVs6JuP94d+PaFgl PeIHnJbWPf2nJ67nYLPPE2mmytpKMgSxDDr9Ruhe2iCR7YxhepI9d59+l7ofkJTpcr+q K7mw== X-Gm-Message-State: ALoCoQkiSBDvlpNy6NcwjjOr7bpafRNlqE/JY6pKBfuPOCxu8h5PV8mlrtYcvNwNIOrGilbu45x+ MIME-Version: 1.0 X-Received: by 10.49.74.138 with SMTP id t10mr45020501qev.21.1386100015947; Tue, 03 Dec 2013 11:46:55 -0800 (PST) Received: by 10.96.245.12 with HTTP; Tue, 3 Dec 2013 11:46:55 -0800 (PST) In-Reply-To: References: Date: Tue, 3 Dec 2013 14:46:55 -0500 Message-ID: Subject: Re: Maximum number of regions for a table? From: "Kevin O'dell" To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=047d7bdc13fe12fc5f04eca68fde X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc13fe12fc5f04eca68fde Content-Type: text/plain; charset=ISO-8859-1 Hi Kim, I would take a look at: http://hadoop-hbase.blogspot.com/2013/01/hbase-region-server-memory-sizing.html On Tue, Dec 3, 2013 at 2:42 PM, Kim Chew wrote: > I am wondering if there is a restrain on the number of regions that a table > could have. For example, if I have a table that grows very fast so the > region keeps splitting, is it possible that the table could have as many > regions as it could until all the resource run out? > > Thanks. > > Kim > -- Kevin O'Dell Systems Engineer, Cloudera --047d7bdc13fe12fc5f04eca68fde--