Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <25160419.82481292206684924.JavaMail.jira@thor>
Date: Sun, 12 Dec 2010 21:18:04 -0500 (EST)
From: "Wang Xu (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1362) Provide volume management
 functionality for DataNode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Wang Xu commented on HDFS-1362:
-------------------------------

Hi Eli, 

This issue likes to be a consequence operation of HDFS-457. After having replaced failed disks or added new disks, this patch can be used to re-install them without restart datanode.

Thanks,
Wang Xu

> Provide volume management functionality for DataNode
> ----------------------------------------------------
>
>                 Key: HDFS-1362
>                 URL: https://issues.apache.org/jira/browse/HDFS-1362
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: data-node
>            Reporter: Wang Xu
>            Assignee: Wang Xu
>         Attachments: HDFS-1362.4_w7001.txt, HDFS-1362.txt, Provide_volume_management_for_DN_v1.pdf
>
>
> The current management unit in Hadoop is a node, i.e. if a node failed, it will be kicked out and all the data on the node will be replicated.
> As almost all SATA controller support hotplug, we add a new command line interface to datanode, thus it can list, add or remove a volume online, which means we can change a disk without node decommission. Moreover, if the failed disk still readable and the node has enouth space, it can migrate data on the disks to other disks in the same node.
> A more detailed design document will be attached.
> The original version in our lab is implemented against 0.20 datanode directly, and is it better to implemented it in contrib? Or any other suggestion?

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