I have been looking into this some more by looking a the output of dfsadmin
-report during the decommissioning process. After a node has been
decommissioned, dfsadmin -report shows that the node is in the
Decommissioned state. The web interface dfshealth.jsp shows it as a dead
node. After I
It looks like the behavior is the same with 0.18.2 and 0.19.0. Even though
I removed the decommissioned node from the exclude file and run the
refreshNode command, the decommissioned node still show up as a dead node.
What I did noticed is that if I leave the decommissioned node in the exclude
, but with
those two additional commands it does.
- Alyssa
From: Bill Au [bill.w...@gmail.com]
Sent: Thursday, January 29, 2009 5:40 PM
To: core-user@hadoop.apache.org
Subject: Re: decommissioned node showing up ad dead node in web based
interface to namenode
I was able to decommission a datanode successfully without having to stop my
cluster. But I noticed that after a node has been decommissioned, it shows
up as a dead node in the web base interface to the namenode (ie
dfshealth.jsp). My cluster is relatively small and losing a datanode will
have
