hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14869) Better request latency histograms
Date Thu, 03 Dec 2015 17:45:11 GMT

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

Hadoop QA commented on HBASE-14869:
-----------------------------------

{color:red}-1 overall{color}.  
        {color:green}+1 core zombie tests -- no zombies!{color}.

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/16754//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/16754//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/16754//artifact/patchprocess/checkstyle-aggregate.html

                Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/16754//console

This message is automatically generated.

> 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: Vikas Vishwakarma
>         Attachments: 14869-test-0.98.txt, 14869-v1-0.98.txt, 14869-v1-2.0.txt, 14869-v2-0.98.txt,
14869-v2-2.0.txt, 14869-v3-0.98.txt, 14869-v4-0.98.txt, 14869-v5-0.98.txt, AppendSizeTime.png,
Get.png
>
>
> 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)

Mime
View raw message