[
https://issues.apache.org/jira/browse/HBASE-21410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669520#comment-16669520
]
stack commented on HBASE-21410:
-------------------------------
bq. But when the number of table is like more than 1000, it seems hard to find
all problematic regions?
That is true. Our UI needs to scale. When there are 1000s of RITs, it draw
little tabs on the bottom. This table stuff should move to another screen
rather than be in the home page? If 1000s of tables, that is another issue? We
have that problem anyways?
For RITs, I think being able to view by table and then for the whole cluster
would be good: i.e. a page listing all Regions that are OPENING in table x,
then another view that is all OPENING regions on the whole cluster?
What is 'RIT Queue'? Do we have to have it along the top? We can't just have
links from this table section?
> 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
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Attachments: 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
>
>
> *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)
