[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192925#comment-17192925
]
Guanghao Zhang commented on HBASE-11288:
----------------------------------------
{quote}Using your definition of specialization (use cases storing data in
“local master region”)
{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}the master won’t scale horizontally among other reasons
{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}In terms of simplicity, I think if you look at both from different
perspectives either one can be seen as simpler than the other.
{quote}
For me, the assignment framework "easy to read/understand" is more important.
{quote}bq. adds master to read/write path, etc
{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}As for “assignment problems” I think we’ve proven through the successful
ITBLL runs that hbase-2 is able to handle the extra tier of assignment
{quote}
Successful ITBLL is great. Sorry for miss this.
> 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)
