[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111992#comment-17111992
]
Francis Christopher Liu commented on HBASE-11288:
-------------------------------------------------
{quote}
Just do not see any difference if we just have a single root region on a region
server? For all the cases, the client will also harmmering the region server
which hosts the root region and bring down all the cluster...
{quote}
IMHO this type of workload is a regionserver responsibility and hence there are
advantages to it being done on the regionserver.
1. 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? In which case it gives simplicity and code
reuse as we are applying one solution to two problems. Although we'd have to
add code for root getting assigned first etc, which I believe should be
relatively straightforward with procedures.
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.
2. 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.
Please correct me if I'm making any wrong assumptions here. Let me know what
you think?
> 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)
