hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lohit Vijayarenu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3736) NullPointerException in INode prevent Namenode from starting
Date Wed, 09 Jul 2008 23:41:31 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612319#action_12612319

Lohit Vijayarenu commented on HADOOP-3736:

bq. Currently the only workaround for this is to re-format HDFS across the cluster. 
There are 2 work arounds for this. 
- You can ignore all the edits which haven't been saved yet. Just replace an empty edits file
and startup the NameNode.
- You can ignore the exception similar to what was suggested by HADOOP-820

HADOOP-3717 has been opened to solve such problems and provide a way for recovery. 

> NullPointerException in INode prevent Namenode from starting
> ------------------------------------------------------------
>                 Key: HADOOP-3736
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3736
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.16.4
>         Environment: CentOS 5, Sun JDK 1.5.0_15
>            Reporter: Xavier Stevens
> After a headnode went down due to a kernel panic, it was restarted.  When trying to restart
the Hadoop process we encountered the following NullPointerException.  It seems this should
be handled more gracefully allowing the Name Node to come up and function while either deleting
or ignoring the problematic INodes.
> 2008-07-09 14:30:11,458 INFO org.apache.hadoop.fs.FSNamesystem: isPermissionEnabled=true
> 2008-07-09 14:30:12,713 ERROR org.apache.hadoop.dfs.NameNode: java.lang.NullPointerException
> 	at org.apache.hadoop.dfs.INodeDirectory.getExistingPathINodes(INode.java:408)
> 	at org.apache.hadoop.dfs.INodeDirectory.getNode(INode.java:357)
> 	at org.apache.hadoop.dfs.INodeDirectory.getNode(INode.java:365)
> 	at org.apache.hadoop.dfs.FSDirectory.unprotectedDelete(FSDirectory.java:458)
> 	at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:537)
> 	at org.apache.hadoop.dfs.FSImage.loadFSEdits(FSImage.java:756)
> 	at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:639)
> 	at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:222)
> 	at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:79)
> 	at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:254)
> 	at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
> 	at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:131)
> 	at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:176)
> 	at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:162)
> 	at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:846)
> 	at org.apache.hadoop.dfs.NameNode.main(NameNode.java:855)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message