[
https://issues.apache.org/jira/browse/HBASE-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824037#comment-16824037
]
Hudson commented on HBASE-21410:
--------------------------------
Results for branch master
[build #954 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/954/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/954//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/954//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/954//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> A helper page that help find all problematic regions and procedures
> -------------------------------------------------------------------
>
> Key: HBASE-21410
> URL: https://issues.apache.org/jira/browse/HBASE-21410
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0, 2.2.0, 2.1.1
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.2
>
> Attachments: HBASE-21410.branch-2.1.001.patch,
> HBASE-21410.branch-2.1.002.patch, HBASE-21410.master.001.patch,
> HBASE-21410.master.002.patch, HBASE-21410.master.003.patch,
> HBASE-21410.master.004.patch, Screenshot from 2018-10-30 19-06-21.png,
> Screenshot from 2018-10-30 19-06-42.png, Screenshot from 2018-10-31
> 10-11-38.png, Screenshot from 2018-10-31 10-11-56.png, Screenshot from
> 2018-11-01 17-56-02.png, Screenshot from 2018-11-01 17-56-15.png
>
>
> *This page is mainly focus on finding the regions stuck in some state that
> cannot be assigned. My proposal of the page is as follows:*
> !Screenshot from 2018-10-30 19-06-21.png!
> *From this page we can see all regions in RIT queue and their related
> procedures. If we can determine that these regions' state are abnormal, we
> can click the link 'Procedures as TXT' to get a full list of procedure IDs to
> bypass them. Then click 'Regions as TXT' to get a full list of encoded region
> names to assign.*
> !Screenshot from 2018-10-30 19-06-42.png!
> *Some region names are covered by the navigator bar, I'll fix it later.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
