[
https://issues.apache.org/jira/browse/HADOOP-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651719#action_12651719
]
Hadoop QA commented on HADOOP-4029:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12394796/HADOOP-4029.patch
against trunk revision 721415.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 2 new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3670/console
This message is automatically generated.
> NameNode should report status and performance for each replica of image and
> log
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4029
> URL: https://issues.apache.org/jira/browse/HADOOP-4029
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
> Assignee: Boris Shkolnik
> Attachments: HADOOP-4029.patch
>
>
> The administrator should have immediate access to the status of each replica.
> In addition to reporting whether the replica is active or not, measured
> performance should be reported so as to indicate whether a replica might
> impact cluster performance or might be in danger of failing.
> We're probably not close to doing automated replica fail over, but we can
> give the administrator some clues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
