[
https://issues.apache.org/jira/browse/HBASE-20603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489613#comment-16489613
]
Andrew Purtell commented on HBASE-20603:
----------------------------------------
bq. I think instead I want to ask: is there a larger time-bound which would be
useful to monitor min/max on? e.g. 4 or 8hr windows
As long as I don't touch FLH itself, then the metrics API is at its leisure to
choose arbitrary points to reset min/max (and all other state carried from old
bins into new bins after snapshot).
I don't think we need to add a feature like this, though, or, at least, where I
work we don't foresee a need for local aggregation of histogram metrics over an
interval longer than the reporting/snapshot interval. We have an external
scalable metrics DB (built on HBase/TSDB FWIW) that will handle such things.
> 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)
