Backup name node stops responding
---------------------------------

                 Key: HDFS-2050
                 URL: https://issues.apache.org/jira/browse/HDFS-2050
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: name-node
    Affects Versions: 0.21.0
         Environment: FreeBSD
            Reporter: Vitalii Tymchyshyn


I've tried to set up backup node on 0.21 and after dome time got:

2011-06-07 20:11:34,820 ERROR 
org.apache.hadoop.hdfs.server.namenode.Checkpointer: Throwable Exception in 
doCheckpoint: 
java.lang.NullPointerException: Panic: parent does not exist
        at 
org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1508)
        at 
org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1522)
        at 
org.apache.hadoop.hdfs.server.namenode.FSDirectory.addNode(FSDirectory.java:1407)
        at 
org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedAddFile(FSDirectory.java:216)
        at 
org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadEditRecords(FSEditLog.java:526)
        at 
org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:411)
        at 
org.apache.hadoop.hdfs.server.namenode.BackupStorage.convergeJournalSpool(BackupStorage.java:333)
        at 
org.apache.hadoop.hdfs.server.namenode.Checkpointer.doCheckpoint(Checkpointer.java:252)
        at 
org.apache.hadoop.hdfs.server.namenode.Checkpointer.run(Checkpointer.java:141)

2011-06-07 20:11:37,072 WARN 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: ReplicationMonitor thread 
received InterruptedException.java.lang.InterruptedException: sleep interrupted
2011-06-07 20:11:37,073 WARN 
org.apache.hadoop.hdfs.server.namenode.DecommissionManager: Monitor 
interrupted: java.lang.InterruptedException: sleep interrupted

The node stopped responding, but did not exit. It seems to work after restart 
(did not try to restart main NameNode).
I've found this: https://issues.apache.org/jira/browse/HDFS-1904
But comments says it affects only 0.23 trunk, so I think this is either 
different bug or at least it should be said it can be reproduced on 0.21.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to