hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5144) manual way of turning on restore of failed storage replicas for namenode
Date Fri, 09 Oct 2009 17:39:31 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robert Chansler updated HADOOP-5144:

    Release Note: New DFSAdmin command -restoreFailedStorage true|false|check sets policy
for restoring failed fsimage/editslog volumes.  (was: This patch added a new DFSAdmin command
[-restoreFailedStorage true|false|check])

Editorial pass over all release notes prior to publication of 0.21.

> 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.
You can reply to this email to add a comment to the issue online.

View raw message