[ https://issues.apache.org/jira/browse/HBASE-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888065#comment-16888065 ]
stack commented on HBASE-22527: ------------------------------- Pushed on branch-2.1 -- tried to fix the single checkstyle long line complaint but messed up on commit -- because I like the patch so much (trying to help out). It won't go into branch-2.0. Skip 2.0? > [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.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)