Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-19285

Add per-table latency histograms

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 1.4.0, 1.3.2, 2.0.0
    • metrics
    • None
    • Reviewed
    • Hide
      Per-RegionServer table latency histograms have been returned to HBase (after being removed due to impacting performance). These metrics are exposed via a new JMX bean "TableLatencies" with the typical naming conventions: namespace, table, and histogram component.
      Show
      Per-RegionServer table latency histograms have been returned to HBase (after being removed due to impacting performance). These metrics are exposed via a new JMX bean "TableLatencies" with the typical naming conventions: namespace, table, and histogram component.

    Description

      HBASE-17017 removed the per-region latency histograms (e.g. Get, Put, Scan at p75, p85, etc)

      HBASE-15518 added some per-table metrics, but not the latency histograms.

      Given the previous conversations, it seems like it these per-table aggregations weren't intentionally omitted, just never re-implemented after the per-region removal. They're some really nice out-of-the-box metrics we can provide to our users/admins as long as it's not detrimental.

      Attachments

        1. HBASE-19285.003.branch-1.3.patch
          33 kB
          Josh Elser
        2. HBASE-19285.002.branch-1.3.patch
          33 kB
          Josh Elser
        3. HBaseTableLatencyMetrics.png
          136 kB
          Josh Elser
        4. HBASE-19285.001.branch-1.3.patch
          31 kB
          Josh Elser

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            elserj Josh Elser
            clayb Clay B.
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment