hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19285) Add per-table latency histograms
Date Tue, 21 Nov 2017 10:21:00 GMT

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

Mikhail Antonov commented on HBASE-19285:
-----------------------------------------

Thanks for the ping (sorry I have been busy lately and didn't have much time to track conversations,
unfortunately..)

I'm all for bringing histograms back in as long, as Andrew said, they aren't prohibitively
expensive (not only in terms of QPS/throughput, but in terms of not causing stalls under high
load - i understand the first condition is much easier to verify than the second, unfortunately).

> 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
>
>         Attachments: HBASE-19285.001.branch-1.3.patch, HBASE-19285.002.branch-1.3.patch,
HBaseTableLatencyMetrics.png
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message