[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183903#comment-17183903
]
Francis Christopher Liu commented on HBASE-11288:
-------------------------------------------------
I see thanks for confirming my understanding of the patch as well as
elaborating on it more [~zhangduo].
Master Local Region is a specialization because it makes root no longer the
same as hbase:meta. It is no longer is a table like meta table: local region,
does not host region on a regionserver, etc. Solutions to root cannot always be
generalized to hbase:meta.
In itself Master Local Region implementation has its merits but when taking it
as part of a whole: the catalog, I’m of the opinion we’d need a compelling
reason to justify the specialization?
I see sounds like you’re implying that a simple api could work for “general
root table” as well? Assuming there is no compelling reason to go with Master
Local Region implementation.
For the purpose of understanding where this discussion is going. Earlier you
mentioned if we could get a reasonable result from the ITBLL run you would
change your mind. Is this still the case?
> 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)
