[
https://issues.apache.org/jira/browse/HBASE-25761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364038#comment-17364038
]
Duo Zhang commented on HBASE-25761:
-----------------------------------
{quote}
If hbase:meta region is not split it operationally will behave pretty much
exactly the same way as before (no operator changes, user changes, etc). As
opposed to having to be aware of the new hbase:root region from the get go.
If hbase:meta region is split. Users/Operators only have to worry about
hbase:meta regions (which one would have to in any split meta implementation),
no new hbase:root table to worry about. Although yes one would need to be aware
of the first meta region getting assigned first.
{quote}
For me, I would define this as a disadvantage...
If we do not split, it just perform like before, so for most cases where meta
is not too large, we can not test the new code. It is easy to finally lead the
feature to die as the most easy way to fix the problem is to not split meta...
We have purged several features in the past already...
And for reviewing and checking in, I do not think it is a big deal, I've been
implementing almost the whole feature on a feature branch already, not very
hard to do it step by step.
Thanks.
> 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
> Assignee: Francis Christopher Liu
> 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)
