[HDFS-3065] HA: Newly active NameNode does not recognize decommissioning DataNode

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: HA branch (HDFS-1623)
• Component/s: ha
• Assignee: Unassigned
• Reporter: Stephen Chu
• Created: 08/Mar/12 19:09
• Updated: 03/Apr/12 18:24

Description

I'm working on a cluster where, originally, styx01 hosts the active NameNode and styx02 hosts the standby NameNode.

In both styx01's and styx02's exclude file, I added the DataNode on styx03.I then ran hdfs dfsadmin -refreshNodes and verified on styx01 NN web UI that the DN on styx03 was decommissioning. After waiting a few minutes, I checked the standby NN web UI (while the DN was decommissioning) and didn't see that the DN was marked as decommissioning.

I executed manual failover, making styx02 NN active and styx01 NN standby. I checked the newly active NN web UI, and the DN was still not marked as decommissioning, even after a few minutes. However, the newly standby NN's web UI still showed the DN as decommissioning.

I added another DN to the exclude file, and executed hdfs dfsadmin -refreshNodes, but the styx02 NN web UI still did not update with the decommissioning nodes.

I failed back over to make styx01 NN active and styx02 NN standby. I checked the styx01 NN web UI and saw that it correctly marked 2 DNs as decommissioning.