[
https://issues.apache.org/jira/browse/HBASE-14282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707166#comment-14707166
]
Andrew Purtell commented on HBASE-14282:
----------------------------------------
This is something we could do for 2.0 maybe.
bq. Not sure if it's possible to do this without changing the metrics names.
And that would mean for sure we can only do it for 2.0. Even then migration of
ops tooling will be painful for everyone.
I'm about to increase our use of Hadoop metrics at least for HBASE-11062.
Until we actually switch away it's the best implementation option since
everything else uses them, and they are how we plumb metrics to JMX.
> Remove metrics2
> ---------------
>
> Key: HBASE-14282
> URL: https://issues.apache.org/jira/browse/HBASE-14282
> Project: HBase
> Issue Type: Improvement
> Components: metrics
> Reporter: Elliott Clark
> Priority: Critical
> Fix For: 2.0.0
>
>
> Metrics2 has a whole bunch of race conditions and weird edges because of all
> of the caching that metrics2 does.
> Additionally tying something so integral to hadoop who has lots of versions
> we support has been a maintenance nightmare. It would allow us to completely
> get rid of the compat modules.
> Rip it out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
