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

Jingyun Tian commented on HBASE-21410:
--------------------------------------

patch for branch-2.1 is uploaded. For branch-2.0, this patch relies on the 
patch from HBASE-21299 and I checked the comments that [~stack] said not going 
back to 2.0 easily. Thus I guess there is no need to fix branch 2.0?

> 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, 2.0.2
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: HBASE-21410.branch-2.1.001.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)

Reply via email to