You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/06/09 00:05:03 UTC

[jira] [Resolved] (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 ]

Andrew Purtell resolved HBASE-3129.
-----------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Nicolas Spiegelberg)

Stale issue. Reopen if still relevant (if there's new activity)

> 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: metrics, regionserver
>    Affects Versions: 0.89.20100924, 0.90.0
>            Reporter: Nicolas Spiegelberg
>            Priority: Minor
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)