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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/10/06 21:23:27 UTC

[jira] [Commented] (HBASE-14386) Reset MutableHistogram's min/max/sum after snapshot

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

stack commented on HBASE-14386:
-------------------------------

Any numbers? Do we need to lock? In the past a mistake in metrics making cost tens of percents of read latency. Thanks.

> Reset MutableHistogram's min/max/sum after snapshot
> ---------------------------------------------------
>
>                 Key: HBASE-14386
>                 URL: https://issues.apache.org/jira/browse/HBASE-14386
>             Project: HBase
>          Issue Type: Bug
>            Reporter: binlijin
>            Assignee: Oliver
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: HBASE-14386.patch
>
>
> Current MutableHistogram do not reset min/max/sum after snapshot, so we affect by historical data. For example when i monitor the QueueCallTime_mean, i see one host's QueueCallTime_mean metric is high, but when i trace the host's regionserver log i see the QueueCallTime_mean has been lower, but the metric is still high.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)