I believe running the following command on namenode should refresh it. 'hadoop dfsadmin -refreshNodes'
Thanks & Regards, Saurabh Bhutyani Call : 9820083104 Gtalk: [email protected] On Thu, Sep 13, 2012 at 11:25 AM, Viji R <[email protected]> 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 <[email protected]> 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 > > " > > > > > > 专注于Mysql,MSSQL,Oracle,Hadoop > > > > > > > > 2012/9/13 Harsh J <[email protected]> > >> > >> the DN only after (2) so it picks up the right mapping an > > > > >
