[
https://issues.apache.org/jira/browse/HBASE-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864512#comment-15864512
]
Hudson commented on HBASE-17611:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.4 #624 (See
[https://builds.apache.org/job/HBase-1.4/624/])
HBASE-17611 Thrift2 per-call latency metrics are capped at ~2 seconds (garyh:
rev bf0c343fb8d869d0c346bea5c8ea5b9e733c9328)
* (edit)
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift2/ThriftHBaseServiceHandler.java
* (edit)
hbase-thrift/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java
> 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.4.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.3.15#6346)
