[
https://issues.apache.org/jira/browse/HBASE-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118545#comment-13118545
]
stack commented on HBASE-4524:
------------------------------
Reasons to let meta split other than because the cluster has millions of
regions:
+ Distribute the load on meta.
+ Its 'catastrophic' if server carrying meta goes away. It'd be *less*
catastrophic if the regionserver were carrying only a piece of meta.
> 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
