[
https://issues.apache.org/jira/browse/HBASE-19285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-19285:
-------------------------------
Attachment: HBASE-19285.001.branch-1.3.patch
HBaseTableLatencyMetrics.png
.001 First stab at implementation -- a regionserver's view of the latencies of
operations against a table. Based on branch-1.3 simply because that's the
earliest potentially relevant branch.
* New mbean specifically to track these latencies
* Tested with an eye towards runtime as well as object creation (to watch for
the per-region performance issues we had previously)
* Included a screenshot of the data being reported
* Includes a config property to turn off the information being collected (in
case it causes problems).
FYI [~mantonov].
> 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,
> 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)
