You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/04/11 12:32:00 UTC

[jira] [Commented] (HBASE-25761) POC: hbase:meta,,1 as ROOT

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

Duo Zhang commented on HBASE-25761:
-----------------------------------

IMO this is even worse than introducing a ROOT region...

If we fully follow the bigtable way, then we need to split the meta region first to separate the special 'ROOT' region, it will break the old client...

In SCP and other places we still need to treat the first meta region specially, which is the same with introducing an extra ROOT region, but the code will be more confusing...

> POC: hbase:meta,,1 as ROOT
> --------------------------
>
>                 Key: HBASE-25761
>                 URL: https://issues.apache.org/jira/browse/HBASE-25761
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Michael Stack
>            Priority: Major
>
> One of the proposals up in the split-meta design doc suggests a sleight-of-hand where the current hard-coded hbase:meta,,1 Region is leveraged to serve as first Region of a split hbase:meta but also does double-duty as 'ROOT'. This suggestion was put aside as a complicating recursion in chat but then Francis noticed on a re-read of the BigTable paper, that this is how they describe they do 'ROOT': "The root tablet is just the first tablet in the METADATA table, but is treated specially -- it is never split..."
> This issue is for playing around with this notion to see what the problems are so can do a better description of this approach here, in the design:
> https://docs.google.com/document/d/11ChsSb2LGrSzrSJz8pDCAw5IewmaMV0ZDN1LrMkAj4s/edit?ts=606c120f#heading=h.ikbhxlcthjle



--
This message was sent by Atlassian Jira
(v8.3.4#803005)