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 817D19B10 for ; Thu, 13 Sep 2012 07:46:31 +0000 (UTC) Received: (qmail 94501 invoked by uid 500); 13 Sep 2012 07:20:27 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 93986 invoked by uid 500); 13 Sep 2012 07:20:22 -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 93895 invoked by uid 99); 13 Sep 2012 07:20:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 07:20:18 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,FSL_RCVD_USER,HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hovlj.ei@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 07:20:13 +0000 Received: by obbtb18 with SMTP id tb18so5196498obb.35 for ; Thu, 13 Sep 2012 00:19:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zztxhofL3DqmhfVoOwaKqj9c6tOOduC4VEQPpM3EMdk=; b=z8HuUpoe6vpQZBn4rgjhs692+eLcJWJK99vSMo2G38DPy5wTK8+gJeS0tmEQEkwqkH 30dGmexWCpwxi+XDfczNZC5xGzkar2/QADfCvgL0kxJlxRYr+yYOEzPye49nVM1Nr/dP I1lPapq+KLn+PF6lgQEwtKp/YggRvMw3wL+Jlo9BjpO8oe3nAdEvQXGWVRtPUn5ag07R m99I6+9vOVxJvWW83/tTPbgXZ1ewffKQNiCoNe7UPJ/KFGj+k08+Z3phiV9y7XfMeeNh 9B0adVmPBDir0Wm0Yd9cHT51J4RQg2mPPO4a5snwFQAk+3HkL52QTanxaxruK5RKScey 4oPw== Received: by 10.60.29.72 with SMTP id i8mr894830oeh.26.1347520792662; Thu, 13 Sep 2012 00:19:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.141.167 with HTTP; Thu, 13 Sep 2012 00:19:21 -0700 (PDT) In-Reply-To: References: From: Jameson Li Date: Thu, 13 Sep 2012 15:19:21 +0800 Message-ID: Subject: Re: rack topology data update To: user@hadoop.apache.org Cc: harsh , viji@cloudera.com, s4saurabh@gmail.com Content-Type: multipart/alternative; boundary=e89a8fb1f8062c924b04c9902217 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb1f8062c924b04c9902217 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Hi Harsh J, Viji R, Saurabh bhutyani, Thanks for all of yours replying. But really the namenode not refresh the rack info. Is my hadoop version issue? My hadoop version is base on hadoop-0.20-append, and have 4 patches on it that I think they are really no matter with the rack awareness. If anytime I add new nodes, and I should restart namenode to refresh the rack info, I will crazy... =D7=A8=D7=A2=D3=DAMysql,MSSQL,Oracle,Hadoop 2012/9/13 Saurabh bhutyani > I believe running the following command on namenode should refresh it. > > 'hadoop dfsadmin -refreshNodes' > > Thanks & Regards, > Saurabh Bhutyani > > Call : 9820083104 > Gtalk: s4saurabh@gmail.com > > > > > On Thu, Sep 13, 2012 at 11:25 AM, Viji R wrote: > >> Hi Jameson, >> >> If the NameNode has cached the wrong value earlier, it will not >> refresh that until you restart it. >> >> On Thu, Sep 13, 2012 at 11:21 AM, Jameson Li wrote: >> > Hi harsh, >> > >> > I have followed your suggestion operation. >> > >> > 1, stop the new datanode.(I have modified the topology file in the >> namenode >> > before.) >> > 2, run 'hadoop dfsadmin -refreshNodes' on the namenode >> > 3, start the new datanode. >> > >> > But it really not update the new topology mapping. >> > It just show the start info in the namenode that: >> > " >> > 2012-09-13 13:44:14,706 INFO org.apache.hadoop.net.NetworkTopology: >> Removing >> > a node: /default-rack/10.0.10.100:50010 >> > 2012-09-13 13:44:14,706 INFO org.apache.hadoop.net.NetworkTopology: >> Adding a >> > new node: /default-rack/10.0.10.100:50010 >> > " >> > >> > >> > =D7=A8=D7=A2=D3=DAMysql,MSSQL,Oracle,Hadoop >> > >> > >> > >> > 2012/9/13 Harsh J >> >> >> >> the DN only after (2) so it picks up the right mapping an >> > >> > >> > > --e89a8fb1f8062c924b04c9902217 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: quoted-printable
Hi  = Harsh J,  Viji R,  Saurabh bhu= tyani,

Thanks for all of yours replying.

But rea= lly the namenode not refresh the rack info.

Is my = hadoop version issue? My hadoop version is base on hadoop-0.20-append, and = have 4 patches on it that I think they are really no matter with the rack a= wareness.

If anytime I add new nodes, and I should restart nameno= de to refresh the rack info, I will crazy...

= =D7=A8=D7=A2=D3=DAMysql,MSSQL,Oracle,Hadoop


2012/9/13 Saurabh bhutyani <s4saurabh= @gmail.com>
I believe running the following command on namenode should refresh it.=

'hadoop dfsadmin -refres= hNodes'

Thanks & Regards,
Saurabh Bhutyani

Call&nbs= p; : 9820083104
Gtalk: s4saurabh@gmail.com

=


On Thu, Sep 13, 2012 at 11:25 AM, Viji R= <viji@cloudera.com> wrote:
hovlj.ei@gmail.com> wrote:
> Hi harsh,
>
> I have followed your suggestion operation.
>
> 1, stop the new datanode.(I have modified the topology file in the nam= enode
> before.)
> 2, run 'hadoop dfsadmin -refreshNodes' on the namenode
> 3, start the new datanode.
>
> But it really not update the new topology mapping.
> It just show the start info in the namenode that:
> "
> 2012-09-13 13:44:14,706 INFO org.apache.hadoop.net.NetworkTopology: Re= moving
> a node: /default-rack/10.0.10.100:50010
> 2012-09-13 13:44:14,706 INFO org.apache.hadoop.net.NetworkTopology: Ad= ding a
> new node: /default-rack/10.0.10.100:50010
> "
>
>
> =D7=A8=D7=A2=D3=DAMysql,MSSQL,Oracle,Hadoop
>
>
>
> 2012/9/13 Harsh J <harsh@cloudera.com>
>>
>> the DN only after (2) so it picks up the right mapping an
>
>


--e89a8fb1f8062c924b04c9902217--