[
https://issues.apache.org/jira/browse/HBASE-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Spiegelberg updated HBASE-3102:
---------------------------------------
Description: Example: a useful metric to observe track is compaction count
+ duration. Since compactions are long running and only happen infrequently,
the avg/opcount stats are should be reset longer than the default polling
period (5 sec). In addition to 'hbase.period', we should allow a different
duration after which long-running metrics should expire. This would also fix
our existing metrics problem where min/max stats are never reset until the
process is restarted/upgraded. (was: A useful metric to observe track is
compaction count + duration. Since compactions are long running and only happen
infrequently, the avg/opcount stats are should be reset longer than the default
polling period (5 sec). In addition to 'hbase.period', we should allow a
different duration after which long-running metrics should expire. This would
also fix our existing metrics problem where min/max stats are never reset until
the process is restarted/upgraded.)
Summary: Enhance HBase rMetrics for Long-running Stats (was: Enhance
HRegionServerMetrics for Long-running Stats)
Note : I put the 2nd patch in Review Board because this was starting to get a
little unwieldy. I added a class PersistentMetricsTimeVaryingRate to abstract
out the persistence code. I still went the derived class way because I got
hung up trying to work with the registration in MetricsMBeanBase.
> Enhance HBase rMetrics for Long-running Stats
> ---------------------------------------------
>
> Key: HBASE-3102
> URL: https://issues.apache.org/jira/browse/HBASE-3102
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
> Fix For: 0.90.0
>
> Attachments: HBASE-3102_90.patch
>
>
> Example: a useful metric to observe track is compaction count + duration.
> Since compactions are long running and only happen infrequently, the
> avg/opcount stats are should be reset longer than the default polling period
> (5 sec). In addition to 'hbase.period', we should allow a different duration
> after which long-running metrics should expire. This would also fix our
> existing metrics problem where min/max stats are never reset until the
> process is restarted/upgraded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
