HBASE-6323 has the first Metrics2 implementation that I've gotten to. We will have to add lots of documentation around hadoop-metrics2.properties and the jmx locations are not consistent, however Metrics2 is much nicer to use for dynamic metrics.
On Mon, Jul 9, 2012 at 12:28 PM, Ted Yu <yuzhih...@gmail.com> wrote: > If I don't get objection by Friday the 13th @ mid night (PST), I will > create a JIRA that marks HBase metric classes that depend on > org.apache.hadoop.metrics.* deprecated. > > Thanks > > On Mon, Jul 9, 2012 at 9:35 AM, Ted Yu <yuzhih...@gmail.com> wrote: > > > Thanks for the response, Jon. > > > > One more detail: the metrics2 classes in hadoop 1.0 and hadoop 2.0 are > > different. Alex is working on a shim layer to make the difference > > transparent. If we were to keep 0.96 metric (1) compatible, we would be > > maintaining 2.5 metric systems. > > > > Cheers > > > > > > On Mon, Jul 9, 2012 at 9:28 AM, Jonathan Hsieh <j...@cloudera.com> wrote: > > > >> I'm ok if we moved solely to metrics2 in 0.96 and if we deprecated in > >> 0.94. > >> > >> Jon. > >> > >> On Sat, Jul 7, 2012 at 7:23 AM, Ted Yu <yuzhih...@gmail.com> wrote: > >> > >> > Hi, > >> > See the following comment for background: > >> > > >> > > >> > https://issues.apache.org/jira/browse/HBASE-4050?focusedCommentId=13408679&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13408679 > >> > > >> > metrics2 framework is in both hadoop 1.0 and hadoop 2.0 > >> > We would like to migrate to metrics2 framework. But maintaining two > >> metrics > >> > frameworks in HBase is costly and results in lower readability. > >> > > >> > However, if you have cluster monitoring tool that depends on (old) > >> metrics > >> > framework, we want to give you smooth migration experience. > >> > > >> > Please provide your opinions on whether (old) metrics framework should > >> be > >> > deprecated in 0.94 or in 0.96. > >> > > >> > Thanks > >> > > >> > >> > >> > >> -- > >> // Jonathan Hsieh (shay) > >> // Software Engineer, Cloudera > >> // j...@cloudera.com > >> > > > > >
