You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by "gmane.org" <sa...@pearsonwholesale.com> on 2011/02/23 15:38:25 UTC
NullPointerException on namenode
I restarted the cluster after the server was way overload by other task and
now I get this
2011-02-23 08:36:18,307 ERROR
org.apache.hadoop.hdfs.server.namenode.NameNode:
java.lang.NullPointerException
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1088)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1100)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.addNode(FSDirectory.java:1003)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedAddFile(FSDirectory.java:206)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:637)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:1034)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:845)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:379)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:99)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:347)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:321)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:267)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:461)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1202)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1211)
any ideas on how to fix or howtos out there I can not find?
Re: NullPointerException on namenode
Posted by "Ravi ." <ip...@gmail.com>.
You need to further dig down in NameNode logs, also make sure that your edit
log and fsimage is not corrupted.
Use backup fsimage & editlog from Secondary name node to restart the cluster
and see if this problem persists.
Looking at stack trace I have a feeling that it's due to the corrupt
file/directory name in your FSimage.
You can use hadoop ovi tool to print FSimage contents.
-
Ravi
On Wed, Feb 23, 2011 at 6:38 AM, gmane.org <sa...@pearsonwholesale.com>wrote:
> I restarted the cluster after the server was way overload by other task and
> now I get this
>
> 2011-02-23 08:36:18,307 ERROR
> org.apache.hadoop.hdfs.server.namenode.NameNode:
> java.lang.NullPointerException
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1088)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1100)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addNode(FSDirectory.java:1003)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedAddFile(FSDirectory.java:206)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:637)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:1034)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:845)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:379)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:99)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:347)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:321)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:267)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:461)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1202)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1211)
>
> any ideas on how to fix or howtos out there I can not find?
>
>