You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 21:23:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-14386.
-----------------------------------------
      Assignee:     (was: Oliver)
    Resolution: Abandoned

> 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: Lijin Bin
>            Priority: Major
>         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
(v8.20.10#820010)