Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 15 Nov 2014 01:28:34 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12753461.1415298757000.506565.1416014914355@Atlassian.JIRA>
In-Reply-To: <JIRA.12753461.1415298757000@Atlassian.JIRA>
References: <JIRA.12753461.1415298757000@Atlassian.JIRA>
 <JIRA.12753461.1415298757054@arcas>
Subject: [jira] [Commented] (HDFS-7374) Allow decommissioning of dead
 DataNodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213247#comment-14213247 ] 

Andrew Wang commented on HDFS-7374:
-----------------------------------

Yea, precisely :) I don't know how realistic this is in an active cluster with lots of failing disks, but it'd fix it for some users at least.

> Allow decommissioning of dead DataNodes
> ---------------------------------------
>
>                 Key: HDFS-7374
>                 URL: https://issues.apache.org/jira/browse/HDFS-7374
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>         Attachments: HDFS-7374-001.patch, HDFS-7374-002.patch
>
>
> We have seen the use case of decommissioning DataNodes that are already dead or unresponsive, and not expected to rejoin the cluster.
> The logic introduced by HDFS-6791 will mark those nodes as {{DECOMMISSION_INPROGRESS}}, with a hope that they can come back and finish the decommission work. If an upper layer application is monitoring the decommissioning progress, it will hang forever.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)