[
https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887124#comment-16887124
]
Sean Busbey commented on HBASE-22527:
-------------------------------------
{code}
55 <section>
56 <h2><a name="rit">Problematic Regions</a></h2>
57 <p>
{code}
We can't anchor this section as "rit" because we already use that below for the
actual rit display. name it "problem-regions" perhaps? fine to fix that on
commit.
otherwise I'm +1. can we get this in all branches-2?
> [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
> 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)
