[
https://issues.apache.org/jira/browse/HBASE-20603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481166#comment-16481166
]
Andrew Purtell edited comment on HBASE-20603 at 5/24/18 1:52 AM:
-----------------------------------------------------------------
Parking a WIP patch that does what I want, but only touches hbase-metrics-api's
Histogram. I don't want to touch FastLongHistogram because it has some legacy
use. Every histogram metric derived from types in hbase-metrics-api, the
majority, especially the call time metrics we are especially interested in,
pick up the behavioral change.
was (Author: apurtell):
Parking a WIP patch that does what I want, but only touches hbase-metrics-api's
Histogram. I don't want to touch FastLongHistogram because it has a lot of
legacy use all over the place. Every histogram metric derived from types in
hbase-metrics-api, the majority, especially the call time metrics we are
especially interested in, pick up the behavioral change.
> Histogram metrics should reset min and max
> ------------------------------------------
>
> Key: HBASE-20603
> URL: https://issues.apache.org/jira/browse/HBASE-20603
> Project: HBase
> Issue Type: Bug
> Components: metrics
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: HBASE-20603-branch-1-WIP.patch
>
>
> It's weird that the bins are reset at every monitoring interval but min and
> max are tracked over the lifetime of the process. Makes it impossible to set
> alarms on max value as they'll never shut off unless the process is
> restarted. Histogram metrics should reset min and max at snapshot time too.
> For discussion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
