Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 79889 invoked from network); 29 Aug 2010 15:54:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Aug 2010 15:54:15 -0000 Received: (qmail 85939 invoked by uid 500); 29 Aug 2010 15:54:15 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 85836 invoked by uid 500); 29 Aug 2010 15:54:15 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 85828 invoked by uid 99); 29 Aug 2010 15:54:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Aug 2010 15:54:14 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 29 Aug 2010 15:54:14 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o7TFrsu5028763 for ; Sun, 29 Aug 2010 15:53:54 GMT Message-ID: <3852181.58301283097234281.JavaMail.jira@thor> Date: Sun, 29 Aug 2010 11:53:54 -0400 (EDT) From: "Wang Xu (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Created: (HDFS-1362) Provide volume management functionality for DataNode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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 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.