You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Janos Gub (JIRA)" <ji...@apache.org> on 2017/04/21 12:47:04 UTC
[jira] [Updated] (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:all-tabpanel ]
Janos Gub updated HBASE-17436:
------------------------------
Attachment: initial.patch
Attaching initial patch. In short I introduced metrics classes for RegionStates, and I update them from the AssignmentManager. In JMX each region's state is booked as a tag. I am not sure if it is the best way to do this, e.g. if the metrics are read and the AssignmentManager is deleting a region I think we can easily run into a ConcurrentModificationException. As an alternative I was thinking about somehow propagating the state to the regions and make this similar to the MetricsRegionAggregateSource. [~tedyu@apache.org] could you please share your thoughts?
> 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
> Attachments: initial.patch
>
>
> [~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.3.15#6346)