[
https://issues.apache.org/jira/browse/HDFS-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-1362:
--------------------------
Comment: was deleted
(was: I will return to the office on January 17th. For urgent matters,
please contact Aparna or Philip L. The week between Christmas and New
Years', your best bet is Chris L.
Thanks,
-- Philip
)
> 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: datanode
> Affects Versions: 0.23.0
> Reporter: Wang Xu
> Assignee: Wang Xu
> Attachments: DataNode Volume Refreshment in HDFS-1362.pdf,
> HDFS-1362.4_w7001.txt, HDFS-1362.5.patch, HDFS-1362.6.patch,
> HDFS-1362.7.patch, HDFS-1362.8.patch, 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
