You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org> on 2012/06/16 00:21:42 UTC
[jira] [Updated] (HBASE-6215) per-request profiling
[ https://issues.apache.org/jira/browse/HBASE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kannan Muthukkaruppan updated HBASE-6215:
-----------------------------------------
Description:
Add ability to get HBase metrics back from an individual request. Apps can use this to track fine-grained metrics (such as server-side latency, block cache access/hit count; sync latency; append latency; etc.) on a per-API call basis. Also, enhance HBase shell to support this feature. [For example, if in the shell we turn profiling on, for all subsequent requests the profiling stats will be pretty printed, or optionally written to a file.]
was:
Add ability to get HBase metrics back from an individual request. Apps can use this to track fine-grained metrics (such as server-side latency, block cache access/hit count; sync latency; append latency; etc.) on a per-API call basis. Also, enhance HBase shell to also support this feature. [For example, if in the shell we turn profiling on, for all subsequent requests the profiling stats will be pretty printed, or optionally written to a file.]
> per-request profiling
> ---------------------
>
> Key: HBASE-6215
> URL: https://issues.apache.org/jira/browse/HBASE-6215
> Project: HBase
> Issue Type: New Feature
> Reporter: Kannan Muthukkaruppan
> Assignee: Aurick Qiao
>
> Add ability to get HBase metrics back from an individual request. Apps can use this to track fine-grained metrics (such as server-side latency, block cache access/hit count; sync latency; append latency; etc.) on a per-API call basis. Also, enhance HBase shell to support this feature. [For example, if in the shell we turn profiling on, for all subsequent requests the profiling stats will be pretty printed, or optionally written to a file.]
--
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