[
https://issues.apache.org/jira/browse/HBASE-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236358#comment-13236358
]
stack commented on HBASE-5533:
------------------------------
The above is all good. I'm not sure how to deprecate a metric. I've not done
that before. We could just turn them off or emit the new stuff on the old
metric name too (which seems silly). If the new are superior, we should just
replace the old w/ the new? Would that be hard to do Shaneal?
> 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
