[
https://issues.apache.org/jira/browse/HBASE-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525514#comment-16525514
]
Andrew Purtell commented on HBASE-20672:
----------------------------------------
FWIW I think this is a valid enhancement. Utility is going to depend on how the
operator consumes the metrics. While these rates can be derived from the
absolute values in the read and write request counters if you have a metrics
database like TSDB it's not possible to see this information at a glance in the
absence of that and if you are building alarms based on scraping JMX metrics
some cooked information like this makes it easy. It's a trade off of course. We
don't want to cook everything, but some information in particular can be
helpful, like this proposal.
> 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)
