Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop, mail # user - Small glitch with setting up two node cluster...only secondary node starts (datanode and namenode don't show up in jps)


Copy link to this message
-
Re: Small glitch with setting up two node cluster...only secondary node starts (datanode and namenode don't show up in jps)
samir das mohapatra 2012-05-30, 13:43
In your logs details  i colud not find the NN stating.

 It is the Problem of NN itself.

  Harsh also  suggested for that same.

On Sun, May 27, 2012 at 10:51 PM, Rohit Pandey <[EMAIL PROTECTED]>wrote:

> Hello Hadoop community,
>
> I have been trying to set up a double node Hadoop cluster (following
> the instructions in -
>
> http://www.michael-noll.com/tutorials/running-hadoop-on-ubuntu-linux-multi-node-cluster/
> )
> and am very close to running it apart from one small glitch - when I
> start the dfs (using start-dfs.sh), it says:
>
> 10.63.88.53: starting datanode, logging to
> /usr/local/hadoop/bin/../logs/hadoop-pandro51-datanode-ubuntu.out
> 10.63.88.109: starting datanode, logging to
>
> /usr/local/hadoop/bin/../logs/hadoop-pandro51-datanode-pandro51-OptiPlex-960.out
> 10.63.88.109: starting secondarynamenode, logging to
>
> /usr/local/hadoop/bin/../logs/hadoop-pandro51-secondarynamenode-pandro51-OptiPlex-960.out
> starting jobtracker, logging to
>
> /usr/local/hadoop/bin/../logs/hadoop-pandro51-jobtracker-pandro51-OptiPlex-960.out
> 10.63.88.109: starting tasktracker, logging to
>
> /usr/local/hadoop/bin/../logs/hadoop-pandro51-tasktracker-pandro51-OptiPlex-960.out
> 10.63.88.53: starting tasktracker, logging to
> /usr/local/hadoop/bin/../logs/hadoop-pandro51-tasktracker-ubuntu.out
>
> which looks like it's been successful in starting all the nodes.
> However, when I check them out by running 'jps', this is what I see:
> 27531 SecondaryNameNode
> 27879 Jps
>
> As you can see, there is no datanode and name node. I have been
> racking my brains at this for quite a while now. Checked all the
> inputs and every thing. Any one know what the problem might be?
>
> --
>
> Thanks in advance,
>
> Rohit
>