[
https://issues.apache.org/jira/browse/HBASE-20654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497572#comment-16497572
]
stack commented on HBASE-20654:
-------------------------------
bq. . We hope quickly find these failded open or failed close and show at web
console in order to assign these regions again by users .
The Master home page shows RITs already? See
./org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.jamon. See how it will
list RIT if any. See the
./org/apache/hadoop/hbase/tmpl/master/AssignmentManagerStatusTmpl.jamon page.
If you want to show RIT elsewhere, use the shell as per Sean above or ask the
Master from remote webconsole. Do
admin.getClusterMetrics(ClusterMetrics.Option.REGIONS_IN_TRANSITION).. It
passes you back a ClusterMetrics instance on which you can do
#getRegionStatesInTransition and it will return List<RegionState> where
RegionState has region names, status, etc. (If need it in hbase1, use old
ClusterStatus object)?
Metrics in hbase are used to keep counts; not data such as region names.
Keeping arbitrary Strings that come and go will bloat our metrics output and
will always be truncated. Metrics are generated on a period regardless of
whether they are read or not whereas asking hbase when you need to draw a
webconsole page is a one-time affair.
Does this help?
> Expose regions in transition thru JMX
> -------------------------------------
>
> Key: HBASE-20654
> URL: https://issues.apache.org/jira/browse/HBASE-20654
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: liubangchen
> Priority: Major
> Attachments: 1.png, HBASE-20654-1.patch, HBASE-20654-2.patch,
> HBASE-20654-3.patch
>
>
> Currently only the count of regions in transition is exposed thru JMX.
> Here is a sample snippet of the /jmx output:
> {code}
> {
> "beans" : [ {
> ...
> }, {
> "name" : "Hadoop:service=HBase,name=Master,sub=AssignmentManager",
> "modelerType" : "Master,sub=AssignmentManager",
> "tag.Context" : "master",
> ...
> "ritCount" : 3
> {code}
> It would be desirable to expose region name, state for the regions in
> transition as well.
> We can place configurable upper bound on the number of entries returned in
> case there're a lot of regions in transition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)