[
https://issues.apache.org/jira/browse/HBASE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204929#comment-13204929
]
Enis Soztutar commented on HBASE-5325:
--------------------------------------
My 2 cents:
bq. @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).
It seems that Hadoop-1.0 includes some of the metrics2 changes but not all, so
I agree that without going full 0.23, it is not possible to use metrics2.
bq. 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'.
With an offline discussion with Hitesh, we completely agree on the roadmap for
managing the cluster configuration in one place, but I think JMX is not
suitable for this. We can keep the current approach of read-only JMX beans, and
deal with the issue of configuration management in another ticket. I'll try to
read up on how other distributed software projects approach this problem.
I totally agree that we might want to aggregate some of the metrics in master,
and possibly redesign the HServerLoad using metrics, but we can deal with that
in yet another issue. Since all of the metrics are collected via MasterMetrics,
and exposed via MasterStatistics, I think we will not need any API change for
that, no?
I think the current patch, as it is, is enough for defining a base for future
work. It only exposes data that is available in the webapi, and with it we
would have 3 API endpoints/JMX beans that we can query relevant info.
HBaseInfo for common information
HBaseMasterInfo for master level status information
MasterStatistics for metrics
> 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
