Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 EBE9610754 for ; Fri, 5 Jul 2013 05:07:01 +0000 (UTC) Received: (qmail 84351 invoked by uid 500); 5 Jul 2013 05:06:55 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 84241 invoked by uid 500); 5 Jul 2013 05:06:54 -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 84232 invoked by uid 99); 5 Jul 2013 05:06:53 -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 05:06:53 +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.180 as permitted sender) Received: from [209.85.128.180] (HELO mail-ve0-f180.google.com) (209.85.128.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jul 2013 05:06:47 +0000 Received: by mail-ve0-f180.google.com with SMTP id pa12so1499777veb.11 for ; Thu, 04 Jul 2013 22:06:26 -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=v3VGpeTPD/caF1QM7FOtoVOQ01ArMbfCZ8NOjWY8fag=; b=Sf+tzom/u4H5oBsERWeZ5xfdlKeuI/qZhBVuxUMoJNI+ijpuTkv8V1tpGDpVKLBpCP jplLy2amkSgTOJMOVKRtH6S4mgFdQ6VU4Onsgx5DbXKYeIB3zDmFgh98y5h5f1I2W4pA 7cV+yrOF9ARVMr77vhuvDq56YisiddZifUH1VT11IgUgQj6tI1norI/faIgQwaOmSiuo w5ckcOxFbrLcMFGywN8EvPf1CCjnMWFZpYod+6qyUZGzejtixVRCzwdxLa7mviE+IT5N nYx+bbmBcUjxIb//0p1agwAs+/RCshVCPUFistW3XZcNEbweF9gqRSwtFrpIkGSRFapP WamA== MIME-Version: 1.0 X-Received: by 10.58.223.238 with SMTP id qx14mr5289056vec.98.1373000786783; Thu, 04 Jul 2013 22:06:26 -0700 (PDT) Received: by 10.220.250.209 with HTTP; Thu, 4 Jul 2013 22:06:26 -0700 (PDT) In-Reply-To: <06006DDA5A27D541991944AC4117E7A96E1CF6C8@szxeml560-mbx.china.huawei.com> References: <06006DDA5A27D541991944AC4117E7A96E1CF5DF@szxeml560-mbx.china.huawei.com> <06006DDA5A27D541991944AC4117E7A96E1CF661@szxeml560-mbx.china.huawei.com> <06006DDA5A27D541991944AC4117E7A96E1CF6C8@szxeml560-mbx.china.huawei.com> Date: Fri, 5 Jul 2013 13:06:26 +0800 Message-ID: Subject: Re: Decomssion datanode - no response From: Azuryy Yu To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e013d06fa2c310904e0bca800 X-Virus-Checked: Checked by ClamAV on apache.org --089e013d06fa2c310904e0bca800 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 issued= , > 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 releate= d > logs in the datanode log. what's wrong?**** > > **** > > ** ** > --089e013d06fa2c310904e0bca800 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Client hasn't any connection 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


--089e013d06fa2c310904e0bca800--