hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "binlijin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14386) Reset MutableHistogram's min/max/sum after snapshot
Date Tue, 22 Sep 2015 09:43:04 GMT

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

binlijin commented on HBASE-14386:

Most of the time we only need to get the read lock, only when snapshot only we need to get
write lock, so i think the lock may not heavy.

> 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

View raw message