Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 8 Sep 2015 16:45:48 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12560803.1339780616000.280529.1441730748071@Atlassian.JIRA>
In-Reply-To: <JIRA.12560803.1339780616000@Atlassian.JIRA>
References: <JIRA.12560803.1339780616000@Atlassian.JIRA>
 <JIRA.12560803.1339780616883@arcas>
Subject: [jira] [Resolved] (HBASE-6215) per-request profiling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)