Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 7 Feb 2012 06:21:00 +0000 (UTC)
From: "stack (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1252481762.6968.1328595660071.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <728242142.5294.1328222213874.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5325) Expose basic information about the
 master-status through jmx beans
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-5325:
------------------------------

@Enis metrics2 seems a bit out there for us (hadoop 0.23?). We want to run on 0.23 and 1.0 and 2.0, etc., so it'd be a while before we could lean on it.  metrics2 has facility that would help? (I've not studied it).

@Hitesh Regards "I am still digging into jmx internals but I could not find anything which mentions it as an option for pushing information.", even if there was a means (IIRC there is but am likely off), I think we'd have master pulling.

bq. Having the master pull information from all region servers using jmx ( or any other point to point protocol ) would likely be a bad idea from a performance point of view.

Currently every regionserver sends status every (configurable) second.  Its a fat Writable serialization of each regionservers counters and current state.  IIRC, this mechanism runs mostly independent and beside our metrics (so there'll be Writable serialization of regionstate and if something like tsdb is running, there'll be a JMX serialization of server stating happening too).  Would be an improvement if we did metrics reporting one way only if possible.

bq. Also, was your intention to have the HMaster be a metric aggregator for the RegionServers' metrics?

It does this now for key stats.

bq. I still need to look at nesting of mbeans from various components and also need to look at the hbase code in more detail to see what kind of management options could be exposed via jmx.

I'd be interested in what you think.  We need to figure being able to config a running cluster; i.e. change Configuration values and have hbase notice.  Having this go via jmx would likely be like taking the 'killarney road to dingle' as my grandma used to say (its shorter if you take the tralee road) so maybe jmx is read-only rather than 'management'.

                
> Expose basic information about the master-status through jmx beans 
> -------------------------------------------------------------------
>
>                 Key: HBASE-5325
>                 URL: https://issues.apache.org/jira/browse/HBASE-5325
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>            Priority: Minor
>             Fix For: 0.94.0
>
>         Attachments: HBASE-5325.1.patch, HBASE-5325.wip.patch
>
>
> Similar to the Namenode and Jobtracker, it would be good if the hbase master could expose some information through mbeans.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira