[
https://issues.apache.org/jira/browse/HDFS-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fengdong Yu updated HDFS-4959:
------------------------------
Description:
There is dfs.hosts.exclude configured before NN start. Active/Standby works
well.
1)Add two datanodes IPAddr to the exclude file on the both Active and Standby
NN.
2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs
in the ActiveNN log. but decommission logs showed in the StandbyNN log.
There is no decommission datanodes showed on the Active NN webUI. but there
does have decommission datanodes showed on the Standby NN webUI.
But the decommission process is very very slow, it indicates it cannot finish
forever.
was:
There is dfs.hosts.exclude configured before NN start. Active/Standby works
well.
1)Add two datanodes IPAddr to the exclude file.
2)run: hdfs dfsadmin -refreshNodes on the Active NN.
There is no
> Decommission data nodes, There is no response
> ---------------------------------------------
>
> Key: HDFS-4959
> URL: https://issues.apache.org/jira/browse/HDFS-4959
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client, namenode
> Affects Versions: 2.0.5-alpha
> Reporter: Fengdong Yu
>
> There is dfs.hosts.exclude configured before NN start. Active/Standby works
> well.
> 1)Add two datanodes IPAddr to the exclude file on the both Active and Standby
> NN.
> 2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs
> in the ActiveNN log. but decommission logs showed in the StandbyNN log.
> There is no decommission datanodes showed on the Active NN webUI. but there
> does have decommission datanodes showed on the Standby NN webUI.
> But the decommission process is very very slow, it indicates it cannot finish
> forever.
--
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
