You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2019/10/08 23:35:00 UTC
[jira] [Resolved] (HBASE-22767) System table RIT STUCK if their
RSGroup has no highest version RSes
[ https://issues.apache.org/jira/browse/HBASE-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Stack resolved HBASE-22767.
-----------------------------------
Fix Version/s: 2.3.0
3.0.0
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to master and branch-2. Let me know if need it elsewhere [~Xiaolin Ha]. Thanks for the patch.
> System table RIT STUCK if their RSGroup has no highest version RSes
> -------------------------------------------------------------------
>
> Key: HBASE-22767
> URL: https://issues.apache.org/jira/browse/HBASE-22767
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> AM chooses highest version region servers as participants for system tables, including META table. If system table group has no highest version region servers, then the reassignment of their regions will be always the BOGUS server defined in RSGroup.
> In our test environment using branch-2.2, we isolate system tables in a rsgroup containing only one server. And when upgrading RSs, we have met the problem that META is always assigned to the BOGUS server while the group server has already been online for a while. META RIT is stuck and can not be recovered by hbck2.
> I made a UT reproduce this problem, steps are:
> 1. add a group, move 1 server to it;
> 2. move meta table to the group;
> 3. restart the group server and downgrade its version;
> 4. meta rit stuck.
>
> ROOT cause is AM filters highest version RSs for system tables. So if we do not change the versions of system table group servers, but upgrade the versions of other group servers, then if there is reassignment for any system tables, such as balancer moving their regions, RIT STUCK!!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)