[
https://issues.apache.org/jira/browse/HADOOP-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031421#comment-13031421
]
Hadoop QA commented on HADOOP-6920:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12478742/hadoop-6920.v6.patch
against trunk revision 1101668.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 12 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/426//console
This message is automatically generated.
> Metrics2: metrics instrumentation
> ---------------------------------
>
> Key: HADOOP-6920
> URL: https://issues.apache.org/jira/browse/HADOOP-6920
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Luke Lu
> Assignee: Luke Lu
> Fix For: 0.23.0
>
> Attachments: hadoop-6920-metrics2-inst-v4.patch, hadoop-6920.v6.patch
>
>
> The jira tracks the metrics instrumentation for the new framework, i.e.,
> porting jvm and rpc metrics to the new framework.
> This issue (esp. the "incompatible change flag") depends on the outcome of
> the discussion (proposed in HADOOP-6728) on whether we should support
> backward compatibility (at some cost.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
