Nick Dimiduk created HBASE-12911:
------------------------------------
Summary: 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
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)
