hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19285) Add per-table latency histograms
Date Thu, 16 Nov 2017 23:44:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-19285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256171#comment-16256171

Andrew Purtell commented on HBASE-19285:

Wouldn't these be as expensive as the per region latency histogram metrics were? Since we
have to track tables region by region and roll up? Do we have an alternate or better metrics
implementation since HBASE-17017?

> Add per-table latency histograms
> --------------------------------
>                 Key: HBASE-19285
>                 URL: https://issues.apache.org/jira/browse/HBASE-19285
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics
>            Reporter: Clay B.
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 2.0.0, 1.4.0, 1.3.3
> HBASE-17017 removed the per-region latency histograms (e.g. Get, Put, Scan at p75, p85,
> 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

This message was sent by Atlassian JIRA

View raw message