[
https://issues.apache.org/jira/browse/HDFS-7411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315051#comment-14315051
]
Tsz Wo Nicholas Sze commented on HDFS-7411:
-------------------------------------------
> ... with pause time being the most important one. ...
It is not necessary the most important in all the cases. Consider a large
cluster with many datanode, say 4000, but few data so that each datanode only
has few number of blocks, say < 100. Then the admin decide to reduce the size
of the cluster dramatically, say 2000. With setting 100k blocks per node, it
could decommission > 1000 nodes per iteration. Is it the intended behavior?
> As usual, I'll sign myself up to fix any issues that surface, so there's no
> worry about ongoing maintenance.
Thanks for signing it up. What if you are unavailable later on? What if there
is a bug you don't know how to fix?
> Refactor and improve decommissioning logic into DecommissionManager
> -------------------------------------------------------------------
>
> Key: HDFS-7411
> URL: https://issues.apache.org/jira/browse/HDFS-7411
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.5.1
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Attachments: hdfs-7411.001.patch, hdfs-7411.002.patch,
> hdfs-7411.003.patch, hdfs-7411.004.patch, hdfs-7411.005.patch,
> hdfs-7411.006.patch, hdfs-7411.007.patch, hdfs-7411.008.patch,
> hdfs-7411.009.patch, hdfs-7411.010.patch
>
>
> Would be nice to split out decommission logic from DatanodeManager to
> DecommissionManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
