[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194141#comment-17194141
]
Francis Christopher Liu commented on HBASE-11288:
-------------------------------------------------
{quote}
If one solution will be used by more and more use cases, it will be not a
specialization and will be generalized for HBase.
{quote}
Understood this definition is different from how I used the term and they
aren't necessarily contradicting. I agree as well that it won’t be a
specialization (your definition) if it’s used by more use cases.
{quote}
Because the root table only have one region, it cannot scale horizontally, too.
If you use read region replica for this, the "master local region" can use read
region replica feature, too. In terms of scalability, "root table" is same with
"master local region".
{quote}
I see I mentioned master scalability with regards to using "master local
region" for other use cases such as replication, etc which might benefit from
horizontal scalability. Although yes replicas/caching will help with cluster
scalability for either implementation (although IMHO operationally “master
local region” requires it and it’s optional for “root table”). Having said that
it's also good to think about whether it's worth it to give the master (which
doesn't scale horizontally) more work when it doesn't need to do it.
{quote}
For me, the assignment framework "easy to read/understand" is more important.
{quote}
Off-hand I think both will be easy to read/understand. For "root table" the
code is basically an extension/intertwining of meta code so if you understand
meta code you will understand root code they’re almost the same.
{quote}
Now the core dependency in read/write path is the ZK. And I thought there are
exist issues about this: HBase should reduce ZK dependency in the future. So
when no ZK dependency, I thought that introduce master to read/write path is
acceptable.
{quote}
I see, I too would like to not expose ZK to the client. Some comments in this
jira is a discussion between me and Andy about using regionserver instead of
the master to provide the bootstrap information. I will work on implementing
that option only if root is not hosted in master as it would no longer make
sense if it is.
> 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)
