Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 11 Aug 2015 17:09:46 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12769727.1422040908000.34402.1439312986763@Atlassian.JIRA>
In-Reply-To: <JIRA.12769727.1422040908000@Atlassian.JIRA>
References: <JIRA.12769727.1422040908000@Atlassian.JIRA>
 <JIRA.12769727.1422040908731@arcas>
Subject: [jira] [Commented] (HBASE-12911) Client-side metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682090#comment-14682090 ] 

Elliott Clark commented on HBASE-12911:
---------------------------------------

Can we please make them pluggable and not drag all of the hadoop metrics in by default.  My experience with the hadoop metrics system has been less than pleasurable and while I really really want the client side metrics, I don't want to have to have any more hadoop metrics in my life. So it would be good to be able to replace it with a different implementation.

So maybe a new maven module that the client can load if configured?

> Client-side metrics
> -------------------
>
>                 Key: HBASE-12911
>                 URL: https://issues.apache.org/jira/browse/HBASE-12911
>             Project: HBase
>          Issue Type: Brainstorming
>          Components: Client, Performance, Usability
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>
> There's very little visibility into the hbase client. Folks who care to add some kind of metrics collection end up wrapping Table method invocations with {{System.currentTimeMillis()}}. For a crude example of this, have a look at what I did in {{PerformanceEvaluation}} for exposing requests latencies up to {{IntegrationTestRegionReplicaPerf}}. The client is quite complex, there's a lot going on under the hood that is impossible to see right now without a profiler. Being a crucial part of the performance of this distributed system, we should have deeper visibility into the client's function.
> I'm not sure that wiring into the hadoop metrics system is the right choice because the client is often embedded as a library in a user's application. We should have integration with our metrics tools so that, i.e., a client embedded in a coprocessor can report metrics through the usual RS channels, or a client used in a MR job can do the same.
> I would propose an interface-based system with pluggable implementations. Out of the box we'd include a hadoop-metrics implementation and one other, possibly [dropwizard/metrics|https://github.com/dropwizard/metrics].
> Thoughts?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)