[
https://issues.apache.org/jira/browse/HBASE-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237406#comment-13237406
]
Shaneal Manek commented on HBASE-5533:
--------------------------------------
Ah, upon further examination, I realized I initially misunderstood what that
those HRegion metrics you pointed out were doing. They are calculating
statistics on a per-CF basis (HBASE-4219), while I thought they were per-RS.
Unfortunately, that means they don't overlap like I thought they did.
I've attached a new patch that applies to TRUNK.
> Add more metrics to HBase
> -------------------------
>
> Key: HBASE-5533
> URL: https://issues.apache.org/jira/browse/HBASE-5533
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.92.2, 0.94.0
> Reporter: Shaneal Manek
> Assignee: Shaneal Manek
> Priority: Minor
> Attachments: BlockingQueueContention.java, HBASE-5533-0.92-v4.patch,
> TimingOverhead.java, hbase-5533-0.92.patch, hbase5533-0.92-v2.patch,
> hbase5533-0.92-v3.patch, hbase5533-0.92-v5.patch, histogram_web_ui.png
>
>
> To debug/monitor production clusters, there are some more metrics I wish I
> had available.
> In particular:
> - Although the average FS latencies are useful, a 'histogram' of recent
> latencies (90% of reads completed in under 100ms, 99% in under 200ms, etc)
> would be more useful
> - Similar histograms of latencies on common operations (GET, PUT, DELETE)
> would be useful
> - Counting the number of accesses to each region to detect hotspotting
> - Exposing the current number of HLog files
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
