Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns;
	h=message-id:date:from:user-agent:mime-version:to:subject:
	references:in-reply-to:content-type:content-transfer-encoding;
	b=c8Ah930Y9LHdUsiyb9IkTjsS3ucIjRRcVvOCxB8aGQ/pzK44WGiTo+oyIxkInoAU
Message-ID: <498B3179.2080201@yahoo-inc.com>
Date: Thu, 05 Feb 2009 10:35:37 -0800
From: Konstantin Shvachko <shv@yahoo-inc.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: core-dev@hadoop.apache.org
Subject: Re: displaying decommissioned node in dfshealth.jsp
References: <3b5f72030902051013r11e6bf8cq4e40cfa6c73b219d@mail.gmail.com>
In-Reply-To: <3b5f72030902051013r11e6bf8cq4e40cfa6c73b219d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Did you look at the name-node web UI?
What does it say about decommissioned nodes?
Thanks,
--Konstantin

Bill Au wrote:
> Right now a decommissioned datanode shows up as a dead datanode in
> dfshealth.jsp.  I went into a case where a datanode failed after I have
> decomissioned another datanode in the same Hadoop cluster.  They both show
> up as dead datanodes, and the operation folks don't know which is which.  I
> noticed that dfsadmin -report does show the admin state of the
> decommissioned datanode as "Decommissioned".  So I am thinking that if we
> add a "Admin State" column in the Dead Datanodes table in dfshealth.jsp
> (similar to the existing Admin State column in the Live Datanodes table), it
> will be clear if a dead datanode was in service or was decommissioned.
> 
> The change/addition to dfshealth.jsp is simple and straight forward.  I am
> willing to submit a patch via jira.  Should I go ahead?
> 
> Bill
>