Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Hargraves, Alyssa" <alyssa@WPI.EDU>
To: "core-user@hadoop.apache.org" <core-user@hadoop.apache.org>
Date: Thu, 29 Jan 2009 17:45:57 -0500
Subject: RE: decommissioned node showing up ad dead node in web based
 	interface to namenode (dfshealth.jsp)
Thread-Topic: decommissioned node showing up ad dead node in web based
 	interface to namenode (dfshealth.jsp)
Thread-Index: AcmCYqj4K65Pz0HUTpiNuRYdjNPR1gAALD92
Message-ID: 
 <97534EA9160306479CFD9FAF444DAF2CD2EFFF75B6@EXCHANGEMAIL.admin.wpi.edu>
References: <3b5f72030901271408o3c968074yfd028be0223a0056@mail.gmail.com>
	 <dd93292a0901271601g33518c41q5b1c0a8158ddee8d@mail.gmail.com>,<3b5f72030901291440ma9894e2l743ab217bf67fe1b@mail.gmail.com>
In-Reply-To: <3b5f72030901291440ma9894e2l743ab217bf67fe1b@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Bill-

I believe once the node is decommissioned you'll also have to run bin/hadoo=
p-daemon.sh start datanode and bin/hadoop-daemon.sh start tasktracker (both=
 run on the slave node, not master) to revive the dead node.  Just removing=
 it from exclude and refreshing doesn't work for me either, but with those =
two additional commands it does.

- Alyssa
________________________________________
From: Bill Au [bill.w.au@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   int=
erface to namenode (dfshealth.jsp)

Not sure why but this does not work for me.  I am running 0.18.2.  I ran
hadoop dfsadmin -refreshNodes after removing the decommissioned node from
the exclude file.  It still shows up as a dead node.  I also removed it fro=
m
the slaves file and ran the refresh nodes command again.  It still shows up
as a dead node after that.

I am going to upgrade to 0.19.0 to see if it makes any difference.

Bill

On Tue, Jan 27, 2009 at 7:01 PM, paul <paulgnyc@gmail.com> wrote:

> Once the nodes are listed as dead, if you still have the host names in yo=
ur
> conf/exclude file, remove the entries and then run hadoop dfsadmin
> -refreshNodes.
>
>
> This works for us on our cluster.
>
>
>
> -paul
>
>
> On Tue, Jan 27, 2009 at 5:08 PM, Bill Au <bill.w.au@gmail.com> wrote:
>
> > I was able to decommission a datanode successfully without having to st=
op
> > 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 performance impact.  So I have a need to monitor the health of my
> > cluster and take steps to revive any dead datanode in a timely fashion.
>  So
> > is there any way to altogether "get rid of" any decommissioned datanode
> > from
> > the web interace of the namenode?  Or is there a better way to monitor
> the
> > health of the cluster?
> >
> > Bill
> >
>