You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2017/11/09 02:39:01 UTC

[jira] [Updated] (HBASE-17611) Thrift 2 per-call latency metrics are capped at ~ 2 seconds

     [ https://issues.apache.org/jira/browse/HBASE-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-17611:
-----------------------------------
    Fix Version/s:     (was: 1.4.0)

> Thrift 2 per-call latency metrics are capped at ~ 2 seconds
> -----------------------------------------------------------
>
>                 Key: HBASE-17611
>                 URL: https://issues.apache.org/jira/browse/HBASE-17611
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics, Thrift
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0, 1.3.1
>
>         Attachments: HBASE-17611.001.patch, HBASE-17611.002.patch
>
>
> Thrift 2 latency metrics are measured in nanoseconds.  However, the duration used for per-method latencies is cast to an int, meaning the values are capped at 2.147 seconds.  Let's use a long instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)