[
https://issues.apache.org/jira/browse/HBASE-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508759#comment-16508759
]
stack commented on HBASE-20672:
-------------------------------
bq, The current metrics ReadRequestCount and WriteRequestCount are essentially
values incremented from the start of the service and hence it makes it
difficult to analyze the current operation load on the region server.
Why is that? What is wrong with taking the current count, letting time pass,
and then taking measure again? What the interval to measure on is up to you (or
your monitoring system). For example,
What is your objective with this change? You do not seem to be showing the new
metrics anywhere in hbase UI, is that so? So what is the change for? Thanks.
Oh, in case it helps, here is why I am having trouble with this change... Here
is a graph that shows hit rates using current counters... TSDB is doing the per
second for me.
!hits1vs2.4.40.400.png!
> Create new HBase metrics ReadRequestRate and WriteRequestRate that reset at
> every monitoring interval
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-20672
> URL: https://issues.apache.org/jira/browse/HBASE-20672
> Project: HBase
> Issue Type: Improvement
> Components: metrics
> Reporter: Ankit Jain
> Assignee: Ankit Jain
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-20672.branch-1.001.patch,
> HBASE-20672.master.001.patch, HBASE-20672.master.002.patch,
> HBASE-20672.master.003.patch, hits1vs2.4.40.400.png
>
>
> Hbase currently provides counter read/write requests (ReadRequestCount,
> WriteRequestCount). That said it is not easy to use counter that reset only
> after a restart of the service, we would like to expose 2 new metrics in
> HBase to provide ReadRequestRate and WriteRequestRate at region server level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
