Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 17 Jun 2012 17:44:43 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <2127835763.23184.1339955083017.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <472530746.68550.1303257365879.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1847) Datanodes should decomission
 themselves on volume failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J updated HDFS-1847:
--------------------------

    Fix Version/s:     (was: 0.24.0)
    
> Datanodes should decomission themselves on volume failure
> ---------------------------------------------------------
>
>                 Key: HDFS-1847
>                 URL: https://issues.apache.org/jira/browse/HDFS-1847
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>            Reporter: Eli Collins
>
> A DN should decommission itself rather than shutdown whenever the configured threshold of volume failures (dfs.datanode.failed.volumes.tolerated) has been reached. This allows the namenode to distinguish between a datanode that might not come back up soon (and will need replication) vs one that is just restarting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira