[
https://issues.apache.org/jira/browse/HBASE-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258394#comment-13258394
]
Elliott Clark commented on HBASE-3614:
--------------------------------------
@Todd the time period is configurable. It's set through the hadoop-metrics
hbase.period. Whenever the thread that publishes metrics comes around the
averages are re-set.
> 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
> Fix For: 0.96.0
>
> Attachments: HBASE-3614-0.patch, HBASE-3614-1.patch,
> HBASE-3614-2.patch, HBASE-3614-3.patch, HBASE-3614-4.patch,
> HBASE-3614-5.patch, HBASE-3614-6.patch, HBASE-3614-7.patch,
> HBASE-3614-8.patch, HBASE-3614-9.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
