You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2010/10/22 19:18:02 UTC
[jira] Updated: (HBASE-3129) Fix Min/Avg/Max Values for FS Latency
Metrics
[ https://issues.apache.org/jira/browse/HBASE-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans updated HBASE-3129:
--------------------------------------
Fix Version/s: (was: 0.89.20100924)
> Fix Min/Avg/Max Values for FS Latency Metrics
> ---------------------------------------------
>
> Key: HBASE-3129
> URL: https://issues.apache.org/jira/browse/HBASE-3129
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.89.20100924, 0.90.0
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
> Priority: Minor
> Fix For: 0.90.0
>
>
> Currently RegionServer FS latency metrics are a little deceiving. Because fs*Latency is only updated during RegionServerMetrics::doUpdates, you are really getting the min/max of the latency average over 'hbase.period' instead of the actual min/max outliers. We should refactor the code so we can display these outliers and reset them every 'hbase.period'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.