You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2018/01/04 03:23:00 UTC

[jira] [Commented] (HBASE-17436) Add facility to provide more information for Other Regions seen on Master UI

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

Appy commented on HBASE-17436:
------------------------------

bq. I will move the json part to the rest endpoint. What should we do with the ui-part of the patch? I think it is a good addition to the UI if exposing the Regionstate enum values is not a problem... Also if we do not want to expose our enum values, should we do some mapping to other values which are "public concepts" just to make users able to get some insight into the state of the regions?

Definitely a good addition to UI!
And given dev discussion, and keeping operators' best interest in mind, let's expose the states as plain strings ;)
And put a note in hbase book what the value means (ref to ascii doc of the class) and explicitly stating that it's private class and since enum values can change anytime, string values can too.

Go for it, make it rest api.



> Add facility to provide more information for Other Regions seen on Master UI
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-17436
>                 URL: https://issues.apache.org/jira/browse/HBASE-17436
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Janos Gub
>              Labels: ui, usability
>             Fix For: 2.0.0
>
>         Attachments: 17436.v10.txt, 17436.v11.txt, 17436.v12.txt, 17436.v9.txt, HBASE-17436-v2.patch, HBASE-17436-v5.patch, HBASE-17436-v6.patch, HBASE-17436-v6.patch, HBASE-17436-v7.patch, HBASE-17436-v8.patch, HBASE-17436.patch, HBASE-17779-v3.patch, HBASE-17779-v4.patch, Screen Shot 2017-04-24 at 8.43.31 PM.png, Screen Shot 2017-04-26 at 4.39.49 PM.png, Screen Shot 2017-11-08 at 10.29.49 AM.png, Screen Shot 2017-11-08 at 10.30.09 AM.png, Screen Shot 2017-11-22 at 4.17.35 PM.png, initial.patch, regionstates.png, table-selected.png, tableregions.png
>
>
> [~rpednekar] and I were looking at a case where the count displayed under Other Regions was high (~1200).
> Since the table page just maintains a count instead of List of region names, it is very difficult for user to determine which regions belong to this category.
> We should provide facility to provide more details for this category (LOG, JMX, etc).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)