[
https://issues.apache.org/jira/browse/HBASE-14869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030186#comment-15030186
]
Lars Hofhansl commented on HBASE-14869:
---------------------------------------
[~vik.karma] offered to finish this up. Thank you, sir!
I think what's left is:
# separate size and time metrics into separate classes (or maybe pass unit and
ranges in, and have a single class)
# use the time/size metrics at the right spots
# come up with different ranges for the size metrics
# do the same for Hadoop1 (at least in 0.98)
# make sure the reported names for the metric values to use make sense (and are
easy to use for machine analysis)
> Better request latency histograms
> ---------------------------------
>
> Key: HBASE-14869
> URL: https://issues.apache.org/jira/browse/HBASE-14869
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Attachments: 14869-test-0.98.txt, 14869-v1-0.98.txt
>
>
> I just discussed this with a colleague.
> The get, put, etc, histograms that each region server keeps are somewhat
> useless (depending on what you want to achieve of course), as they are
> aggregated and calculated by each region server.
> It would be better to record the number of requests in certainly latency
> bands in addition to what we do now.
> For example the number of gets that took 0-5ms, 6-10ms, 10-20ms, 20-50ms,
> 50-100ms, 100-1000ms, > 1000ms, etc. (just as an example, should be
> configurable).
> That way we can do further calculations after the fact, and answer questions
> like: How often did we miss our SLA? Percentage of requests that missed an
> SLA, etc.
> Comments?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
