[
https://issues.apache.org/jira/browse/HBASE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated HBASE-5325:
-------------------------------
Attachment: HBASE-5325.1.patch
Based on earlier comments, I made some modifications to the original patch I
had and added a minor impl for the RegionServer.
@Stack, thanks for the comments. Having each component potentially implements
its own beans to expose information ( and potentially allow the object to be
managed ) would likely be a good direction to go into.
However, I had some questions in terms of using jmx to exchange information
between the master and the region servers. I am still digging into jmx
internals but I could not find anything which mentions it as an option for
pushing information. 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. Also, was your intention to have the HMaster
be a metric aggregator for the RegionServers' metrics? Just wondering whether
this would be something which is better left to be dealt with by other metric
aggregation systems? Having this data available in a central place like the
HMaster definitely helps but it also requires a lot of overhead to collect and
aggregate the required information.
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. Any pointers would be helpful.
> 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: Bug
> Reporter: Hitesh Shah
> Priority: Minor
> 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
