[
https://issues.apache.org/jira/browse/HDFS-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007097#comment-13007097
]
Todd Lipcon commented on HDFS-1362:
-----------------------------------
I used to manage a fairly small cluster of storage heavy non-Hadoop nodes in a
previous life. We used SATA hotswap pretty extensively there and it worked
"fairly well". About one out of ten times "scsiadd" wouldn't find the new
drives and we'd have to reboot the box.
This was 4 years ago or so, so things are likely improved by now.
> 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
> Affects Versions: 0.23.0
> Reporter: Wang Xu
> Assignee: Wang Xu
> Fix For: 0.23.0
>
> 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.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
