hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10436) hbase 0.96+ jmx does not have regionserver info any more.
Date Wed, 29 Jan 2014 21:34:14 GMT

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

Elliott Clark commented on HBASE-10436:

I'm -1 any patch that goes directly to JMX to expose data.
I'm also -1 any patch that adds back in any locks into the metrics by default.

bq.Metrics are exposed via JMX but other things and can be exposed via JMX as well.
But you're not exposing anything that the hadoop metrics system can't export.

bq.I'm not sure I'm parsing the last two sentences correctly – are you saying if I added
a conf setting to optionally make the new bean with restored data not show up you'd be ok?

Sources are things in metrics2 that expose data.  If you don't register a source they aren't
available and are never polled. So I'm saying that if you add a source that only registers
itself with metrics2 if the user asks for it then it seems better.  Also this functionality
should be deprecated as soon as it goes in.

bq.How do I get the list of regionservers?
{code}cat $HBASE_HOME/conf/regionservers{code}

bq.Tangentially related. I just submitted a patch to the OpenTSDB tcollector framework, to
make it work with 0.96+ HBase metrics.

I did too but mine was pretty invasive.  Lets hope that yours gets more love.

> hbase 0.96+ jmx does not have regionserver info any more.
> ---------------------------------------------------------
>                 Key: HBASE-10436
>                 URL: https://issues.apache.org/jira/browse/HBASE-10436
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0, 0.96.0, 0.99.0
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>            Priority: Critical
>         Attachments: hbase-10436.patch, hbase-10436.v2.patch
> HBase 0.96's refactored jmx beans do not contain the master's list of dead region servers
and live regionservers with load info.  HBase 0.94 did (though in a single monolithic blob).
> This JMX interface should be considered as much of an API as the the normal wire or java
api.  Dropping values from this was done without deprecation and the removal of this information
is a functional regression.
> We should provide the information in the 0.96+ JMX.  HBase 0.94 had a  monolithic JMX
blob ("hadoop:service=Master,name=Master")  that contained a lot of information, including
the regionserver list and the cached regionserver load for each region  found on the master
webpage.  0.96+ refactored jmx this into several jmx beans which could be selectively retrieved.
 These include:
> * hadoop:service=HBase,name=Master,sub=AssignmentManager
> * hadoop:service=HBase,name=Master,sub=Balancer
> * hadoop:service=HBase,name=Master,sub=Server
> * hadoop:service=HBase,name=Master,sub=FileSystem
> Specifically the (Hadoop:service=HBase,name=Master,sub=Server) listing that used to contain
regionservers and deadregionservers in jmx were replaced in   with numRegionServers and numDeadRegionservers
which only contain counts.  
> I propose just adding another mbean called "RegionServers" under the bean: "hadoop:service=HBase,name=Master,sub=RegionServers"

This message was sent by Atlassian JIRA

View raw message