You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Francis Liu (JIRA)" <ji...@apache.org> on 2018/03/12 23:49:00 UTC
[jira] [Updated] (HBASE-19285) Add per-table latency histograms
[ https://issues.apache.org/jira/browse/HBASE-19285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis Liu updated HBASE-19285:
--------------------------------
Fix Version/s: (was: 1.3.3)
1.3.2
> 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.2
>
> 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, 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
(v7.6.3#76005)