You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/07/24 00:13:00 UTC

[jira] [Resolved] (HBASE-22527) [hbck2] Add a master web ui to show the problematic regions

     [ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guanghao Zhang resolved HBASE-22527.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.6
                   2.2.1
                   2.0.6
                   2.3.0
                   3.0.0
     Release Note: 
Add a new master web UI to show the potentially problematic opened regions. There are three case:
1. Master thought this region opened, but no regionserver reported it.
2. Master thought this region opened on Server1, but regionserver reported Server2
3. More than one regionservers reported opened this region

> [hbck2] Add a master web ui to show the problematic regions
> -----------------------------------------------------------
>
>                 Key: HBASE-22527
>                 URL: https://issues.apache.org/jira/browse/HBASE-22527
>             Project: HBase
>          Issue Type: Sub-task
>          Components: hbase-operator-tools, hbck2
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>         Attachments: HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.0.001.patch, HBASE-22527.branch-2.0.002.patch, HBASE-22527.branch-2.1.001.patch, HBASE-22527.branch-2.1.002.patch, HBASE-22527.branch-2.1.003.patch, HBASE-22527.master.001.patch, HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, HBASE-22527.master.004.patch, HBASE-22527.master.addendum.patch
>
>
> On our cluster which based 2.2.0, we found one problem: there are some opened regions which had wrong regionserver in meta. The regionserver is not exist. We used hbck2 to fix them by the following steps.
>  # disable table
>  # bypass the stucked close region procedure (as the target regionserver is not exist) and disable table procedure.
>  # setRegionState to CLOSED.
>  # setTableState to DISABLED.
>  # enable table
> We found this problem by scan the hbase:meta. I thought we should add this feature to hbck2. The we can use hbck2 to find this problem. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)