[
https://issues.apache.org/jira/browse/HBASE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418486#comment-13418486
]
Elliott Clark commented on HBASE-6411:
--------------------------------------
For my opinion this removes most abstraction of the actual metrics2
implementation, which was something I liked about the first approach. It would
be possible for someone to implement their own metrics1 implementation with the
earlier approach. This approach metrics2 code and classes are seeping into the
hbase-server code. In addition there are a lot more moving parts and a lot more
code than is needed if more code is moved into the compat modules. I'll post a
patch that shows what I'm thinking in a little bit.
> Move Master Metrics to metrics 2
> --------------------------------
>
> Key: HBASE-6411
> URL: https://issues.apache.org/jira/browse/HBASE-6411
> Project: HBase
> Issue Type: Sub-task
> Reporter: Elliott Clark
> Assignee: Alex Baranau
> Attachments: HBASE-6411_concept.patch
>
>
> Move Master Metrics to metrics 2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
