Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <379217260.1257983080021.JavaMail.jira@brutus>
Date: Wed, 11 Nov 2009 23:44:40 +0000 (UTC)
From: "Erik Steffl (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-457) better handling of volume failure in
 Data Node storage
In-Reply-To: <1817020889.1246388327191.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Erik Steffl updated HDFS-457:
-----------------------------

    Attachment: jira.HDFS-457.branch-0.20-internal.patch

> better handling of volume failure in Data Node storage
> ------------------------------------------------------
>
>                 Key: HDFS-457
>                 URL: https://issues.apache.org/jira/browse/HDFS-457
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>             Fix For: 0.21.0
>
>         Attachments: HDFS-457-1.patch, HDFS-457-2.patch, HDFS-457-2.patch, HDFS-457-2.patch, HDFS-457-3.patch, HDFS-457.patch, jira.HDFS-457.branch-0.20-internal.patch, TestFsck.zip
>
>
> Current implementation shuts DataNode down completely when one of the configured volumes of the storage fails.
> This is rather wasteful behavior because it  decreases utilization (good storage becomes unavailable) and imposes extra load on the system (replication of the blocks from the good volumes). These problems will become even more prominent when we move to mixed (heterogeneous) clusters with many more volumes per Data Node.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.