Home Forums HDFS Namenode of Hadoop Crash?

This topic contains 1 reply, has 2 voices, and was last updated by  Larry Liu 1 year, 5 months ago.

  • Creator
    Topic
  • #17830

    Hi I am running Hadoop-1.0.3 from last 1 month but today I got following error at namelog logs:
    2013-03-18 11:11:40,910 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Registered FSNamesystemStateMBean and NameNodeMXBean
    2013-03-18 11:11:40,928 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: Caching file names occuring more than 10 times
    2013-03-18 11:11:40,936 INFO org.apache.hadoop.hdfs.server.common.Storage: Number of files = 156
    2013-03-18 11:11:40,958 INFO org.apache.hadoop.hdfs.server.common.Storage: Number of files under construction = 0
    2013-03-18 11:11:40,958 INFO org.apache.hadoop.hdfs.server.common.Storage: Image file of size 23325 loaded in 0 seconds.
    2013-03-18 11:11:40,962 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: java.lang.NullPointerException
    at org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1099)
    at org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1111)
    at org.apache.hadoop.hdfs.server.namenode.FSDirectory.addNode(FSDirectory.java:1014)
    at org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedAddFile(FSDirectory.java:208)
    at org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:629)
    at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:1021)
    at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:839)

    How to resolve it? I have restarted it manu times but got same problem.

    Thanks in advance.

Viewing 1 replies (of 1 total)

The topic ‘Namenode of Hadoop Crash?’ is closed to new replies.

  • Author
    Replies
  • #17868

    Larry Liu
    Moderator

    Hi, Bhushan

    From the error log, it seems there are some issue with loadFSImage. Do you Secondary Namenode running? If you do, please try following:

    1. Create dfs.name.dir on your new namenode (please backup the older information. it must be empty)
    2. Make sure fs.checkpoint.dir is pointed at your last known good copy
    3. Start the namenode with the -importCheckpoint option

    Please let us know how’s going.

    Thanks
    Larry

    Collapse
Viewing 1 replies (of 1 total)