[ https://issues.apache.org/jira/browse/HDFS-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191467#comment-13191467
]
Hadoop QA commented on HDFS-2825:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12511547/hdfs-2825.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 21 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 appears to introduce 1 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/1796//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1796//artifact/trunk/hadoop-hdfs-project/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1796//console
This message is automatically generated.
> Add test hook to turn off the writer preferring its local DN
> ------------------------------------------------------------
>
> Key: HDFS-2825
> URL: https://issues.apache.org/jira/browse/HDFS-2825
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: hdfs-2825.txt, hdfs-2825.txt
>
>
> Currently, the default block placement policy always places the first replica in the
pipeline on the local node if there is a valid DN running there. In some network designs,
within-rack bandwidth is never constrained so this doesn't give much of an advantage. It would
also be really useful to disable this for MiniDFSCluster tests, since currently if you start
a multi-DN cluster and write with replication level 1, all of the replicas go to the same
DN.
> _[per discussion below, this was changed to not add a config, but only to add a hook
for testing]_
--
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
|