[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112019#comment-17112019
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
{quote}
AFAIK hbase:meta today is getting hammered? If so, we'll likely want to fix
that if we haven't already? If so then whatever fix/enhancement we did the root
table can take advantage of as well?
{quote}
The solution is to make meta splittable... But this is not possible for root
table right?
{quote}
Although we'd have to add code for root getting assigned first etc, which I
believe should be relatively straightforward with procedures.
{quote}
I do not think so... You can see the comment of
finishActiveMasterInitialization method, we have already done lots of magics to
make master start up possible, which heavily depend on the order of
initializing different resources...
{quote}
On the other hand if use the master and backup masters we will be giving them a
new specialized responsibility, which will introduce new specialized code. And
then we would need to introduce more code for the master(s) to not get hammered.
{quote}
The logic is separated so I do not think it will be a big problem. And for me,
with very little code change, I could even use lvs to spread the load to lots
of special services which are only used for locating meta. But if we expose a
raw region to user, then it will be hard to inject a cache or proxy...
{quote}
>From an operations perspective it would be easier for operations folks to
>reason about things as the way both catalog tiers are handled are the same and
>so the way to manage them if there are issues are the same.
{quote}
Well, for me I would say they are not the same... The location for root is on
zk while meta is in root, and root can not be split but meta can...
> 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)
