HBase
  1. HBase
  2. HBASE-3129

Fix Min/Avg/Max Values for FS Latency Metrics

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 0.89.20100924, 0.90.0
    • Fix Version/s: None
    • Component/s: metrics, regionserver
    • Labels:
      None

      Description

      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'

        Issue Links

          Activity

          Hide
          Nicolas Spiegelberg added a comment -

          HBASE-1956 introduced the FS latency metrics.

          Show
          Nicolas Spiegelberg added a comment - HBASE-1956 introduced the FS latency metrics.
          Hide
          stack added a comment -

          Is there a patch for this? If not, will punt to 0.92.

          Show
          stack added a comment - Is there a patch for this? If not, will punt to 0.92.
          Hide
          Nicolas Spiegelberg added a comment -

          0.92 punt is fine

          Show
          Nicolas Spiegelberg added a comment - 0.92 punt is fine
          Hide
          stack added a comment -

          Punting.

          Show
          stack added a comment - Punting.
          Hide
          stack added a comment -

          Moving out of 0.92. Move it back in if you think differently.

          Show
          stack added a comment - Moving out of 0.92. Move it back in if you think differently.
          Hide
          stack added a comment -

          Moving out of 0.92. Move it back in if you think differently.

          Show
          stack added a comment - Moving out of 0.92. Move it back in if you think differently.
          Hide
          Andrew Purtell added a comment -

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

          Show
          Andrew Purtell added a comment - Stale issue. Reopen if still relevant (if there's new activity)

            People

            • Assignee:
              Unassigned
              Reporter:
              Nicolas Spiegelberg
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development