You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/08 18:45:48 UTC
[jira] [Resolved] (HBASE-6215) per-request profiling
[ https://issues.apache.org/jira/browse/HBASE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-6215.
--------------------------
Resolution: Incomplete
Lets go HTrace route for this (no progress on a native hbase per-request tracking). Resolving as incomplete
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)