[
https://issues.apache.org/jira/browse/HDFS-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996814#comment-12996814
]
Hadoop QA commented on HDFS-1300:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12459401/HDFS-1300.3.patch
against trunk revision 1072023.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 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 (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 failed these core unit tests:
org.apache.hadoop.cli.TestHDFSCLI
org.apache.hadoop.hdfs.server.datanode.TestBlockRecovery
org.apache.hadoop.hdfs.TestFileConcurrentReader
-1 contrib tests. The patch failed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/191//testReport/
Findbugs warnings:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/191//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/191//console
This message is automatically generated.
> Decommissioning nodes does not increase replication priority
> ------------------------------------------------------------
>
> Key: HDFS-1300
> URL: https://issues.apache.org/jira/browse/HDFS-1300
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.20.1, 0.20.2, 0.20.3, 0.20-append, 0.21.0, 0.22.0
> Reporter: Dmytro Molkov
> Assignee: Dmytro Molkov
> Attachments: HDFS-1300.2.patch, HDFS-1300.3.patch, HDFS-1300.patch
>
>
> Currently when you decommission a node each block is only inserted into
> neededReplications if it is not there yet. This causes a problem of a block
> sitting in a low priority queue when all replicas sit on the nodes being
> decommissioned.
> The common usecase for decommissioning nodes for us is proactively exclude
> them before they went bad, so it would be great to get the blocks at risk
> onto the live datanodes as quickly as possible.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
