[
https://issues.apache.org/jira/browse/HADOOP-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675363#action_12675363
]
Hadoop QA commented on HADOOP-5258:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12400558/HADOOP-5258.patch
against trunk revision 746166.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 15 new or modified tests.
+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 does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-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/3887/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3887/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3887/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3887/console
This message is automatically generated.
> Provide dfsadmin functionality to report on namenode's view of network
> topology
> -------------------------------------------------------------------------------
>
> Key: HADOOP-5258
> URL: https://issues.apache.org/jira/browse/HADOOP-5258
> Project: Hadoop Core
> Issue Type: New Feature
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Attachments: HADOOP-5258.patch, HADOOP-5258.patch
>
>
> As discussed in HADOOP-4954, it would be useful to be able to query the
> namenode to its current view on the network topology of racks and datanodes.
> This would allow ops to compare what the namenode sees with what they expect
> it to see.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
