[
https://issues.apache.org/jira/browse/HDFS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009731#comment-13009731
]
Tsz Wo (Nicholas), SZE commented on HDFS-1773:
----------------------------------------------
In {{removeDecomNodeFromDeadList(..)}},
- remove public.
- {{hostsReader.getHosts()}} is independent of the nodes. If it is empty,
{{removeDecomNodeFromDeadList(..)}} can return immediately. So we should check
it before the loop.
- {{fsn}} is not a parameter.
{code}
+ * @param fsn, FSNamesystem
{code}
> Remove a datanode from cluster if include list is not empty and this datanode
> is removed from both include and exclude lists
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-1773
> URL: https://issues.apache.org/jira/browse/HDFS-1773
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 0.20.203.1
> Environment: branch-20-security
> Reporter: Tanping Wang
> Assignee: Tanping Wang
> Priority: Minor
> Fix For: 0.20.4
>
> Attachments: HDFS-1773-2.patch, HDFS-1773.patch
>
>
> Our service engineering team who operates the clusters on a daily basis
> founds it is confusing that after a data node is decommissioned, there is no
> way to make the cluster forget about this data node and it always remains in
> the dead node list.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
