hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19285) Add per-table latency histograms
Date Thu, 30 Nov 2017 22:53:04 GMT

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

Josh Elser commented on HBASE-19285:

bq. +1 but with my earlier caveat:

Thanks. Still completely understand. Am ready to push to 1.3, 1.4 and branch-1.

[~stack], you want for 2.0-beta1? I need to resolve merge conflicts and rerun my experiment
(can turn around by tmrw, I hope).

> 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,
HBASE-19285.003.branch-1.3.patch, HBaseTableLatencyMetrics.png
> 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