Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27976108DA for ; Fri, 5 Jul 2013 06:56:10 +0000 (UTC) Received: (qmail 62429 invoked by uid 500); 5 Jul 2013 06:56:02 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 62299 invoked by uid 500); 5 Jul 2013 06:56:00 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 62289 invoked by uid 99); 5 Jul 2013 06:55:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 06:55:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of azuryyyu@gmail.com designates 209.85.128.175 as permitted sender) Received: from [209.85.128.175] (HELO mail-ve0-f175.google.com) (209.85.128.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 06:55:54 +0000 Received: by mail-ve0-f175.google.com with SMTP id da11so1551804veb.34 for ; Thu, 04 Jul 2013 23:55:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=7cn6D/Yp3k/LQQh6iwFgrkqMsipPWHP6f34PsXR4PIc=; b=u2EkqeSqPoPW98OXhjoiOfuSCLXUhW10Kutco453eCpIkKXGr04SUPMLQHkqdyHvub ya6wYu+OHCODom3pfeOUcNpVle62NeowK5OTbEBll3ZMf9jtFoUKoKbJelJCL5Pca+5U nAgQAHHuwrAgxVTFsjsqS0vjhjULne8eQaj0J/JpY02qEIAqAHBT/FQHv9eICdYEFMck vIXQJKM8K6NNztx2pLtv/wCPMQYWG+IMqZV8nZfHuad8z8YWW/nsdPLvUtbEjoAVve0J dZ97ACjkEDjFqSnoPNM6P2GjkEbS2K0VuvjROkYA6s5TH0JGLjokU5CFzCXucnouz+A7 F1WQ== MIME-Version: 1.0 X-Received: by 10.52.94.211 with SMTP id de19mr4754559vdb.59.1373007333638; Thu, 04 Jul 2013 23:55:33 -0700 (PDT) Received: by 10.220.250.209 with HTTP; Thu, 4 Jul 2013 23:55:33 -0700 (PDT) In-Reply-To: References: <06006DDA5A27D541991944AC4117E7A96E1CF5DF@szxeml560-mbx.china.huawei.com> <06006DDA5A27D541991944AC4117E7A96E1CF661@szxeml560-mbx.china.huawei.com> <06006DDA5A27D541991944AC4117E7A96E1CF6C8@szxeml560-mbx.china.huawei.com> Date: Fri, 5 Jul 2013 14:55:33 +0800 Message-ID: Subject: Re: Decomssion datanode - no response From: Azuryy Yu To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf307cfec6654a8204e0be2e45 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307cfec6654a8204e0be2e45 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I filed this issue at : https://issues.apache.org/jira/browse/HDFS-4959 On Fri, Jul 5, 2013 at 1:06 PM, Azuryy Yu wrote: > Client hasn't any connection problem. > > > On Fri, Jul 5, 2013 at 12:46 PM, Devaraj k wrote: > >> And also could you check whether the client is connecting to NameNode >> or any failure in connecting to the NN.**** >> >> ** ** >> >> Thanks**** >> >> Devaraj k**** >> >> ** ** >> >> *From:* Azuryy Yu [mailto:azuryyyu@gmail.com] >> *Sent:* 05 July 2013 09:15 >> >> *To:* user@hadoop.apache.org >> *Subject:* Re: Decomssion datanode - no response**** >> >> ** ** >> >> I added dfs.hosts.exclude before NN started.**** >> >> **** >> >> and I updated /usr/local/hadoop/conf/dfs_exclude whith new hosts, but It >> doesn't decomssion. **** >> >> ** ** >> >> On Fri, Jul 5, 2013 at 11:39 AM, Devaraj k wrote:= * >> *** >> >> When did you add this configuration in NN conf? **** >> >> >> dfs.hosts.exclude >> /usr/local/hadoop/conf/dfs_exclude >> **** >> >> **** >> >> If you have added this configuration after starting NN, it won=92t take >> effect and need to restart NN.**** >> >> **** >> >> If you have added this config with the exclude file before NN start, you >> can update the file with new hosts and refreshNodes command can be issue= d, >> then newly updated the DN=92s will be decommissioned.**** >> >> **** >> >> Thanks**** >> >> Devaraj k**** >> >> **** >> >> *From:* Azuryy Yu [mailto:azuryyyu@gmail.com] >> *Sent:* 05 July 2013 08:48 >> *To:* user@hadoop.apache.org >> *Subject:* Re: Decomssion datanode - no response**** >> >> **** >> >> Thanks Devaraj,**** >> >> **** >> >> There are no any releated logs in the NN log and DN log.**** >> >> **** >> >> On Fri, Jul 5, 2013 at 11:14 AM, Devaraj k wrote:= * >> *** >> >> Do you see any log related to this in Name Node logs when you issue >> refreshNodes dfsadmin command?**** >> >> **** >> >> Thanks**** >> >> Devaraj k**** >> >> **** >> >> *From:* Azuryy Yu [mailto:azuryyyu@gmail.com] >> *Sent:* 05 July 2013 08:12 >> *To:* user@hadoop.apache.org >> *Subject:* Decomssion datanode - no response**** >> >> **** >> >> Hi,**** >> >> I am using hadoop-2.0.5-alpha, and I added 5 datanodes into dfs_exclude, >> **** >> >> **** >> >> hdfs-site.xml:**** >> >> >> dfs.hosts.exclude >> /usr/local/hadoop/conf/dfs_exclude >> **** >> >> **** >> >> then:**** >> >> hdfs dfsadmin -refreshNodes**** >> >> **** >> >> but there is no decomssion nodes showed on the webUI. and not any >> releated logs in the datanode log. what's wrong?**** >> >> **** >> >> ** ** >> > > --20cf307cfec6654a8204e0be2e45 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable


On Fri,= Jul 5, 2013 at 1:06 PM, Azuryy Yu <azuryyyu@gmail.com> wro= te:
Client hasn't any conne= ction problem.


On Fri, Jul 5, 2013 at 12:46 PM, Devaraj= k <devaraj.k@huawei.com> wrote:

And also could you c= heck whether the client is connecting to NameNode or any failure in connect= ing to the NN.

=A0

Thanks=

Devaraj k<= /u>

=A0

From: Azuryy Yu [m= ailto:azuryyyu@gmai= l.com]
Sent: 05 July 2013 09:15


To: user= @hadoop.apache.org
Subject: Re: Decomssion datanode - no response

=A0

I added dfs.hosts.exclude before NN started.<= u>

=A0

and I updated /usr/local/hadoop/conf/dfs_exclude whi= th new hosts, but It doesn't decomssion.

=A0

On Fri, Jul 5, 2013 at 11:39 AM, Devaraj k <devaraj.k@huawei.com> wrote:

When did you add thi= s configuration in NN conf?

=A0 <property>
=A0=A0=A0 <name>dfs.hosts.exclude</name>
=A0=A0=A0 <value>/usr/local/hadoop/conf/dfs_exclude</value>
=A0 </property>

=A0=

If you have added th= is configuration after starting NN, it won=92t take effect and need to rest= art NN.

=A0=

If you have added th= is config with the exclude file before NN start, you can update the file wi= th new hosts and refreshNodes command can be issued, then newly updated the D= N=92s will be decommissioned.

=A0=

Thanks=

Devaraj k<= /u>

=A0=

From: Azuryy Yu [m= ailto:azuryyyu@gmai= l.com]
Sent: 05 July 2013 08:48
To: user= @hadoop.apache.org
Subject: Re: Decomssion datanode - no response<= /p>

=A0

Thanks Devaraj,

=A0

There=A0are no any releated logs in the NN log and D= N log.

=A0

On Fri, Jul 5, 2013 at 11:14 AM, Devaraj k <devaraj.k@huawei.com> wrote:

Do you see any log r= elated to this in Name Node logs when you issue refreshNodes dfsadmin comma= nd?

=A0=

Thanks=

Devaraj k<= /u>

=A0=

From: Azuryy Yu [m= ailto:azuryyyu@gmai= l.com]
Sent: 05 July 2013 08:12
To: user= @hadoop.apache.org
Subject: Decomssion datanode - no response

=A0

Hi,

I am using hadoop-2.0.5-alpha, and I added 5 datanod= es into dfs_exclude,

=A0

hdfs-site.xml:

=A0 <property>
=A0=A0=A0 <name>dfs.hosts.exclude</name>
=A0=A0=A0 <value>/usr/local/hadoop/conf/dfs_exclude</value>
=A0 </property>

=A0

then:

hdfs dfsadmin -refreshNodes

=A0

but there is no decomssion nodes showed on the webUI= . and not any releated logs in the datanode log. what's wrong?

=A0

=A0



--20cf307cfec6654a8204e0be2e45--