[
https://issues.apache.org/jira/browse/HBASE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201010#comment-13201010
]
Hitesh Shah commented on HBASE-5325:
------------------------------------
Forgot to mention another point with respect to an earlier comment by @stack.
Is one of the items pending in the backlog to change the region servers to push
more information about their state to Zookeeper? If that is the case, pulling
it into the master from there and exposing it via another bean should be
trivial. But like I said, if the data being pushed is more metric-centric, it
will be interesting to see what overhead the master would need to incure to
aggregate all the metrics and keep them in sync on a regular interval.
> 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