hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4214) Per-region request counters should be clearer about scope
Date Sat, 28 Jan 2017 20:37:25 GMT

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

stack commented on HBASE-4214:

[~awked06] What is wanted here is some editorial. Do what you think best and then make it
consistent in itself and across metrics. I think original point is that any pretense at total
read/write over the life of the cluster is not possible given region move resets the counter.

> 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

View raw message