[
https://issues.apache.org/jira/browse/HADOOP-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675609#action_12675609
]
Hadoop QA commented on HADOOP-5144:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12400622/Hadoop-5144-2.patch
against trunk revision 746340.
+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 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 passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3896/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3896/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3896/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3896/console
This message is automatically generated.
> manual way of turning on restore of failed storage replicas for namenode
> ------------------------------------------------------------------------
>
> Key: HADOOP-5144
> URL: https://issues.apache.org/jira/browse/HADOOP-5144
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: Hadoop-5144-1.patch, Hadoop-5144-2.patch,
> Hadoop-5144.patch
>
>
> when HADOOP-4885 is implemented and committed we will automatic facility to
> restore failed storage replicas for namenode. Currently it is controlled by
> configuration file.
> But since it is quite a "sensitive" feature we might want to have a manual
> way of turning it on. (i.e. starting with the feature turned off, and turn it
> on when needed).
> we can use hadoop dfsadmin script to do this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
