[jira] [Commented] (HBASE-4214) Per-region request counters should be clearer about scope

["Sahil Aggarwal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15844004#comment-15844004 ] 

Sahil Aggarwal commented on HBASE-4214:
---------------------------------------

Will changing the heading from 'Read Request Count' -> 'Total Read requests' and 'Write RequestCount' -> 'Total Write Requests' help here? 

Moreover, to get Read/Write count per second can't we use MetricsRegionServerWrapperImpl to use Map<Region,ReadsPerSecond>/Map<Region,WritesPerSecond>  and calculate it the way we are calculating 'Requests per second' for a region server ? 

> 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: 2.0.0
>            Reporter: Todd Lipcon
>            Priority: Trivial
>              Labels: beginner
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)