[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164372#comment-17164372
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
{quote}
What value are we getting out of having a specialized solution for root instead
of fixing it for both the catalog tables (root and meta) as a whole and is it
worth it?
{quote}
I think I have answered this question many times... There is no such 'general'
solution yet, but we already have a framework to support the 'specialized'
solution, and it has already been implemented in HBASE-24459, and the long term
solution is HBASE-24753.
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.
Anyway, let's wait for the ITBLL result first. And then we could discuss again.
Thanks.
> 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
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
