[
https://issues.apache.org/jira/browse/HDFS-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296755#comment-15296755
]
John Zhuge commented on HDFS-7374:
----------------------------------
{color:red}WARNING{color}: as already pointed out by [~xyao], due to a typo in
HDFS-7374 commit message, there are 2 commits with the message prefix
"HDFS-7373":
{noformat}
c0d666c HDFS-7373. Clean up temporary files after fsimage transfer failures.
Contributed by Kihwal Lee
5bd048e HDFS-7373. Allow decommissioning of dead DataNodes. Contributed by Zhe
Zhang.
{noformat}
> Allow decommissioning of dead DataNodes
> ---------------------------------------
>
> Key: HDFS-7374
> URL: https://issues.apache.org/jira/browse/HDFS-7374
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Zhe Zhang
> Assignee: Zhe Zhang
> Fix For: 2.7.0
>
> Attachments: HDFS-7374-001.patch, HDFS-7374-002.patch,
> HDFS-7374.003.patch
>
>
> We have seen the use case of decommissioning DataNodes that are already dead
> or unresponsive, and not expected to rejoin the cluster.
> The logic introduced by HDFS-6791 will mark those nodes as
> {{DECOMMISSION_INPROGRESS}}, with a hope that they can come back and finish
> the decommission work. If an upper layer application is monitoring the
> decommissioning progress, it will hang forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
