You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/11 20:42:00 UTC
[jira] [Resolved] (HBASE-20265) Host regions in other rsgroup when all region servers in a rsgroup are all down
[ https://issues.apache.org/jira/browse/HBASE-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-20265.
-----------------------------------------
Resolution: Won't Fix
> 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
(v8.20.7#820007)