Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 1 Oct 2011 01:08:45 +0000 (UTC)
From: "Todd Lipcon (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2135840395.14285.1317431325838.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <495772952.13758.1317422030650.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4524) support for more than one region in
 .META. table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118613#comment-13118613 ] 

Todd Lipcon commented on HBASE-4524:
------------------------------------

My opinion is that we shouldn't necessarily design for the 10,000 node cluster yet :) We'll hit other scalability issues somewhere along the line with that, too.

bq.  If we somehow need to put 100K bytes for each region in .META. table

Why would we need so much data per region? 1K seems much more reasonable.

                
> support for more than one region in .META. table
> ------------------------------------------------
>
>                 Key: HBASE-4524
>                 URL: https://issues.apache.org/jira/browse/HBASE-4524
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>
> It seems there are some assumptions in the code that .META. table only has one region FIRST_META_REGIONINFO in the following areas:
> 1) .META. table update with user region info.
> 2) .META. regions assignment.
> 3) .META. table split handling.
> Perhaps we don't have such requirement until we scale to really large number of regions like 1M.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira