You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yu Li (JIRA)" <ji...@apache.org> on 2015/11/22 12:50:10 UTC

[jira] [Commented] (HBASE-14869) Better request latency histograms

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

Yu Li commented on HBASE-14869:
-------------------------------

{quote}
It would be better to record the number of requests in certainly latency bands in addition to what we do now
{quote}
+1, agree it could better show SLA status this way.

OTOH, I think we should take call queue wait time into account rather than simply request-handling time, which I believe could better reflect the latency client senses. 

> Better request latency histograms
> ---------------------------------
>
>                 Key: HBASE-14869
>                 URL: https://issues.apache.org/jira/browse/HBASE-14869
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Lars Hofhansl
>
> 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)