[
https://issues.apache.org/jira/browse/HBASE-25695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25695.
-----------------------------------
Fix Version/s: 2.3.6
2.4.3
2.5.0
3.0.0-alpha-1
Hadoop Flags: Reviewed
Assignee: Michael Stack
Resolution: Fixed
Pushed to branch-2.3+. Thanks for review [~ndimiduk]
> Link to the filter on hbase:meta from user tables panel on master page
> ----------------------------------------------------------------------
>
> Key: HBASE-25695
> URL: https://issues.apache.org/jira/browse/HBASE-25695
> Project: HBase
> Issue Type: Sub-task
> Components: UI
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3, 2.3.6
>
> Attachments: image-2021-03-24-21-41-11-393.png,
> image-2021-03-24-21-42-16-355.png, image-2021-03-24-21-43-24-426.png
>
>
> This is follow-on to the parent issue that added nice filtering mechanism on
> hbase:meta table. Parent allows finding all Regions in Table XYZ with state
> OPENING or FAILED_CLOSED.
> The user table panel on the master home page has counts of Regions in each
> state. The opening and closing counts actually have links under them but they
> are useless currently as they only show RITs that are CLOSING or OPENING;
> good but not comprehensive enough.
> This PR adds links under all counts so you can see all CLOSING Regions
> whether RIT or not; useful when doing fixup on a corrupt cluster. Adds a bit
> of help text that tells users about the filter-on-meta feature too.
> Here is how the panel currently looks:
> !image-2021-03-24-21-41-11-393.png!
> Here is what it looks like now with the bit of help text
> !image-2021-03-24-21-42-16-355.png!
> When you click on the CLOSED number -- '1' in this case -- this where you go
> to:
> !image-2021-03-24-21-43-24-426.png!
> i..e. lists all Regions in the TestTable that are in the CLOSED state (not
> very pretty with the 'Table Stats' and 'Table Regions' preamble but better
> than what was there before).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
