[
https://issues.apache.org/jira/browse/HBASE-16636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated HBASE-16636:
--------------------------------
Priority: Major (was: Minor)
> Regions in Transition counts wrong (zero) in HMaster /jmx, prevents detecting
> Regions Stuck in Transition
> ---------------------------------------------------------------------------------------------------------
>
> Key: HBASE-16636
> URL: https://issues.apache.org/jira/browse/HBASE-16636
> Project: HBase
> Issue Type: Bug
> Components: UI
> Affects Versions: 1.1.2
> Environment: HDP 2.3.2
> Reporter: Hari Sekhon
> Priority: Major
> Attachments: Regions_in_Transition_UI.png, ritCountOverThreshold.png
>
>
> I've discovered that the Region in Transition counts are wrong in the HMaster
> UI /jmx page.
> The /master-status page clearly shows 3 regions stuck in transition but the
> /jmx page I was monitoring reported 0 for ritCountOverThreshold.
> {code}
> }, {
> "name" : "Hadoop:service=HBase,name=Master,sub=AssignmentManger",
> "modelerType" : "Master,sub=AssignmentManger",
> "tag.Context" : "master",
> ...
> "ritOldestAge" : 0,
> "ritCountOverThreshold" : 0,
> ...
> "ritCount" : 0,
> {code}
> I have a nagios plugin I wrote which was checking this which I've since had
> to rewrite to parse the /master-status page instead (the code is in
> check_hbase_regions_stuck_in_transition.py at
> https://github.com/harisekhon/nagios-plugins).
> I'm attaching screenshots of both /master-status and /jmx to show the
> difference in the 2 pages on the HMaster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
