[
https://issues.apache.org/jira/browse/HBASE-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440564#comment-13440564
]
Lars Hofhansl commented on HBASE-4214:
--------------------------------------
This is true for a bunch of other counters as well.
Did we tackle this already with Metrics2?
> Per-region request counters should be clearer about scope
> ---------------------------------------------------------
>
> Key: HBASE-4214
> URL: https://issues.apache.org/jira/browse/HBASE-4214
> Project: HBase
> Issue Type: Bug
> Components: metrics, regionserver
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Fix For: 0.96.0
>
>
> In testing trunk, I noticed that per-region request counters shown on
> table.jsp are lifetime-scoped, rather than per-second or some other time
> range. However, I'm pretty sure they reset when the region is moved. So, it's
> hard to use them to judge relative hotness of regions from the web UI without
> hooking it up to something lik OpenTSDB
--
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
