[
https://issues.apache.org/jira/browse/HBASE-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256122#comment-13256122
]
Enis Soztutar commented on HBASE-3614:
--------------------------------------
This is fine for JMX, but these per-region metrics will be exposed via the
Hadoop metrics system as well right? If so, the large number of regions and the
fact that regions are dynamic would make it useless for ganglia (or similar).
So, I think we should either not expose them through the hadoop metrics, but do
itJMX only, or make per-region metrics configurable IMO.
> Expose per-region request rate metrics
> --------------------------------------
>
> Key: HBASE-3614
> URL: https://issues.apache.org/jira/browse/HBASE-3614
> Project: HBase
> Issue Type: Improvement
> Components: metrics, regionserver
> Reporter: Gary Helmling
> Assignee: Elliott Clark
> Priority: Minor
> Attachments: HBASE-3614-0.patch, HBASE-3614-1.patch,
> HBASE-3614-2.patch, Screen Shot 2012-04-17 at 2.41.27 PM.png
>
>
> We currently export metrics on request rates for each region server, and this
> can help with identifying uneven load at a high level. But once you see a
> given server under high load, you're forced to extrapolate based on your
> application patterns and the data it's serving what the likely culprit is.
> This can and should be much easier if we just exported request rate metrics
> per-region on each server.
> Dynamically updating the metrics keys based on assigned regions may pose some
> minor challenges, but this seems a very valuable diagnostic tool to have
> available.
--
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
