[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111071#comment-17111071
]
Duo Zhang commented on HBASE-11288:
-----------------------------------
{quote}
1. Large batch jobs that does lookups on an hbase table in tasks would hit it
on startup. Same for large application restarts (eg storm topologies, etc).
2. In the event of failure degradation is not as graceful, as if clients are
not able to find meta regions they will start hammering the master when the
master is already busy trying to recover the cluster.
3. Generally just misbehaving actors (eg poorly written applications) or buggy
third party client implementations that users attempt to use.
{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...
My plan is to let client only contact active master for root table first, and
later, as you said, cache the content for root table in backup master and let
client go to backup masters as much as possible.
> 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)
