Hi,
yes, I find the reason because of the following issue.
'org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory
/usr/local/hadoop/yarn/yarn_data/tmp/dfs/name is in an inconsistent state"
Formatted the HDFS again and fixed the issue.
jps
3774 Jps
3701 NameNode
regards
On 28 Nov, 2013, at 1:25 pm, Harsh J <[email protected]> wrote:
> Yes you should expect to see a NameNode separately available but
> apparently its dying out. Check the NN's log on that machine to see
> why.
>
> On Thu, Nov 28, 2013 at 8:37 AM, Ascot Moss <[email protected]> wrote:
>> Hi,
>>
>> I am new to 2.2.0, after running the following command to start the first
>> namenode, I used jps to check the cluster:
>>
>>
>> ./sbin/hadoop-daemon.sh --script hdfs start namenode
>> starting namenode, logging to
>> /usr/local/hadoop/yarn/hadoop//logs/hadoop-hduser-namenode-hd01.emblocsoft.net.out
>> jps
>> 3405 Jps
>> 3132 DataNode
>>
>>
>> The name of ID 3132 is DataNode, is this correct as I expected something
>> like "3132 NameNode"? does it mean that the following two commands are doing
>> the same thing in 2.2.0?
>>
>> ./sbin/hadoop-daemon.sh --script hdfs start namenode
>> ./sbin/hadoop-daemon.sh --script hdfs start datanode
>>
>>
>> regards
>>
>
>
>
> --
> Harsh J
