[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175238#comment-17175238
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
I’m just a bit surprised that with so many code in place we still do not
support meta split yet? I tried to write a UT to test split based on your
branch and found that the region server will reject the request.
And what do you think of my post above?
I think there is a bias in our discussion, that ROOT 'must be a table'. If we
take a look from the client interface, you can see that, now in
ConnectionRegistry, we have a method to get the location of the single meta
region, it is considered as the 'bootstrap information' of a hbase cluster.
After meta can be split, the only difference is that, we should allow users to
get addresses for different meta regions. We could still consider this as the
'bootstrap information'. From the client side, we do not care how to store the
data of ROOT. If we think from this direction, distributing the load of ROOT,
is exactly the same with distributing the load of the 'bootstrap information',
which is exactly what we have done in
HBASE-18095.
> Splittable Meta
> ---------------
>
> Key: HBASE-11288
> URL: https://issues.apache.org/jira/browse/HBASE-11288
> Project: HBase
> Issue Type: Umbrella
> Components: meta
> Reporter: Francis Christopher Liu
> Assignee: Francis Christopher Liu
> Priority: Major
> Attachments: jstack20200807_bad_rpc_priority.txt, root_priority.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
