[
https://issues.apache.org/jira/browse/HDFS-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872850#action_12872850
]
Hadoop QA commented on HDFS-1161:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12445707/hdfs-1161-6.patch
against trunk revision 949043.
+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 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 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 failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/383/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/383/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/383/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/383/console
This message is automatically generated.
> Make DN minimum valid volumes configurable
> ------------------------------------------
>
> Key: HDFS-1161
> URL: https://issues.apache.org/jira/browse/HDFS-1161
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 0.21.0, 0.22.0
>
> Attachments: hdfs-1161-1.patch, hdfs-1161-2.patch, hdfs-1161-3.patch,
> hdfs-1161-4.patch, hdfs-1161-5.patch, hdfs-1161-6.patch
>
>
> The minimum number of non-faulty volumes to keep the DN active is hard-coded
> to 1. It would be useful to allow users to configure this value so the DN
> can be taken offline when eg half of its disks fail, otherwise it doesn't get
> reported until it's down to it's final disk and suffering degraded
> performance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
