You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/06/03 05:19:00 UTC

[jira] [Commented] (HBASE-22527) [hbck2] check the regions which opened on an inconsistent regionserver with meta

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

Sean Busbey commented on HBASE-22527:
-------------------------------------

why the table disable/enable steps?

> [hbck2] check the regions which opened on an inconsistent regionserver with meta
> --------------------------------------------------------------------------------
>
>                 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
>            Priority: Major
>
> 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.3#76005)