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

["Guanghao Zhang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886915#comment-16886915 ] 

Guanghao Zhang edited comment on HBASE-22527 at 7/17/19 10:48 AM:
------------------------------------------------------------------

{quote}Is this still page still available when master in maintain mode?
{quote}
I tried it on our staging cluster with maintain mode and it is available.


was (Author: zghaobac):
I tried it on our staging cluster and it is available.

> [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: Improvement
>          Components: hbase-operator-tools, hbck2
>            Reporter: Guanghao Zhang
>            Assignee: Guanghao Zhang
>            Priority: Major
>         Attachments: HBASE-22527.master.001.patch, HBASE-22527.master.002.patch, HBASE-22527.master.003.patch, HBASE-22527.master.004.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)