Ronald Macmaster created HBASE-18409:
----------------------------------------
Summary: Migrate Client Metrics from codahale to hbase-metrics
Key: HBASE-18409
URL: https://issues.apache.org/jira/browse/HBASE-18409
Project: HBase
Issue Type: Bug
Components: Client, java, metrics
Affects Versions: 2.0.0-alpha-1
Reporter: Ronald Macmaster
Currently, the metrics for hbase-client are tailored for reporting via a
client-side JMX server.
The MetricsConnection handles the metrics management and reporting via the
metrics platform from codahale. This approach worked well for hbase-1.3.1 when
the metrics platform was still relatively young, but it could be improved by
using the new hbase-metrics-api.
However, now that we have an actual hbase-metrics-api that master,
regionserver, zookeeper, and others use, it would be good to also allow the
client to leverage the metrics-api. Then, the client could also report its
metrics via Hadoop's metrics2 if desired or through another platform that
utilizes the hbase-metrics-api. If left alone, client metrics will continue to
be only barely visible through a client-side JMX server.
The migration to the new metrics-api could be done by simply changing the
Metrics data types from codahale types to hbase-metrics types without changing
the metrics signatures of MetricsConnection unless completely necessary. The
codahale MetricsRegistry would also have to be exchanged for a hbase-metrics
MetricsRegistry.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
