Re: namenode -upgrade problem

2009-08-05 Thread Aaron Kimball
Are you sure you stopped all the daemons? Use 'sudo jps' to make sure :) - Aaron On Mon, Aug 3, 2009 at 7:26 PM, bharath vissapragada bharathvissapragada1...@gmail.com wrote: Todd thanks for replying .. I stopped the cluster and issued the command bin/hadoop namenode -upgrade and iam

Re: namenode -upgrade problem

2009-08-05 Thread bharath vissapragada
yes .. I have stopped all the daemons ... when i use jps ...i get only ... pid Jps Actually .. i upgraded the version from 18.2 to 19.x on the same path of hdfs .. is it a problem? On Wed, Aug 5, 2009 at 11:02 PM, Aaron Kimball aa...@cloudera.com wrote: Are you sure you stopped all the

Re: namenode -upgrade problem

2009-08-05 Thread Aaron Kimball
The only time you would need to upgrade is if you've increased the Hadoop version but are retaining the same HDFS :) So, that's the normal case. What does netstat --listening --numeric --program report? - Aaron On Wed, Aug 5, 2009 at 10:53 AM, bharath vissapragada

namenode -upgrade problem

2009-08-03 Thread bharath vissapragada
Hi all , I have noticed some problem in my cluster when i changed the hadoop version on the same DFS directory .. The namenode log on the master says the following .. ile system image contains an old layout version -16. An upgrade to version -18 is required. Please restart NameNode with

Re: namenode -upgrade problem

2009-08-03 Thread bharath vissapragada
Todd thanks for replying .. I stopped the cluster and issued the command bin/hadoop namenode -upgrade and iam getting this exception 09/08/04 07:52:39 ERROR namenode.NameNode: java.net.BindException: Problem binding to master/10.2.24.21:54310 : Address already in use at