[
https://issues.apache.org/jira/browse/HADOOP-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754579#comment-13754579
]
Hudson commented on HADOOP-5144:
--------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #317 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/317/])
HADOOP-5144. Move change from 3.0 to 2.3.0 release section (suresh:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1518907)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> 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 Common
> Issue Type: Improvement
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Fix For: 0.21.0
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
