[
https://issues.apache.org/jira/browse/HBASE-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411622#comment-16411622
]
Dave Latham commented on HBASE-20265:
-------------------------------------
If all region servers hosting the system tables go down, then the system tables
become unavailable. For that reason, it would likely be good to choose servers
for that group to get a high degree of availability. It's similar to how you
may want to setup your zookeeper quorum, or configure your HDFS Namenodes.
You could choose to have 2 or 3 nodes dedicated to running Master processes and
Region Servers in a dedicated group for system tables.
> Host regions in other rsgroup when all region servers in a rsgroup are all
> down
> -------------------------------------------------------------------------------
>
> Key: HBASE-20265
> URL: https://issues.apache.org/jira/browse/HBASE-20265
> Project: HBase
> Issue Type: Improvement
> Components: rsgroup
> Reporter: Xiang Li
> Priority: Critical
>
> We met the following scenario in our production system:
> rsgroup A hosts user table 1 as well as system tables (let's say
> hbase:rsgroup, or hbase:meta). Several heavy reads on user table 1 make all
> region servers within rsgroup A crash. As a result, the system tables have no
> host.
> Under such scenario, we could manually move the system tables to another
> rsgroup.
> But what about:
> We provide an affinity or last resort. When all region servers in rsgroup A
> crash, rsgroup B, as rsgroup A's affinity, will take over all tables of
> rsgroup A, or at least, some important tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
