[ https://issues.apache.org/jira/browse/HDFS-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252164#comment-13252164 ]
Hadoop QA commented on HDFS-3256: --------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12522367/HDFS-3256.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified test files. +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 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2256//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2256//console This message is automatically generated. > HDFS considers blocks under-replicated if topology script is configured with > only 1 rack > ---------------------------------------------------------------------------------------- > > Key: HDFS-3256 > URL: https://issues.apache.org/jira/browse/HDFS-3256 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.0.0 > Reporter: Aaron T. Myers > Assignee: Aaron T. Myers > Attachments: HDFS-3256.patch, HDFS-3256.patch > > > HDFS treats the mere presence of a topology script being configured as > evidence that there are multiple racks. If there is in fact only a single > rack, the NN will try to place the blocks on at least two racks, and thus > blocks will be considered to be under-replicated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira