[
https://issues.apache.org/jira/browse/HBASE-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920602#action_12920602
]
Gary Helmling commented on HBASE-3102:
--------------------------------------
Actually I think extending (or reimplementing due to private access
constraints) a MetricsTimeVaryingRate class may be the best approach
given what the base hadoop classes allow. Then implement the interval
checking in the class pushMetric() or intervalHeartbeat(). We already
provide our own metric class in o.a.h.h.metrics.MetricsRate.
When you mention introspection problems do you mean in
MetricsMBeanBase? We extend that as well in o.a.h.h.metrics to get
around explicit type checking in the base class and allow
MetricsRate. Or is there another location where the hadoop classes do
the same thing?
On Oct 12, 2010, at 3:03 PM, "Nicolas Spiegelberg (JIRA)" <[email protected]
> Enhance HRegionServerMetrics 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
>
>
> 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.
