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 Fu-Ming Tsai <sa...@gmail.com> on 2009/12/16 02:42:19 UTC
error message when executing SecondaryNameNode
Hello, all,
I tried to execute 2 SecondaryNamenode in my env. However, one worked
fine but the other one failed.
>From the log file, I found the following message.
2009-12-15 15:25:19,429 ERROR
org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: Throwable
Exception in doCheckpoint:
2009-12-15 15:25:19,430 ERROR
org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode:
java.lang.NullPointerException
at org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1006)
at org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:992)
at org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:966)
at org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:953)
at org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:696)
at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:992)
at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.doMerge(SecondaryNameNode.java:590)
at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.access$000(SecondaryNameNode.java:473)
at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doMerge(SecondaryNameNode.java:350)
at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:314)
at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.run(SecondaryNameNode.java:225)
at java.lang.Thread.run(Thread.java:619)
I'm not sure what it happened. Did anyone encounter this problem before??
Best regards,
Fu-Ming
Re: error message when executing SecondaryNameNode
Posted by Fu-Ming Tsai <sa...@gmail.com>.
Thanks for your help, Todd,
It happens whenever I restart SecondaryNamenode.
But what I'm curious is why the other host can work fine. Did you
encounter this problem?
Best regards,
Fu-Ming
On Thu, Dec 17, 2009 at 12:59 AM, Todd Lipcon <to...@cloudera.com> wrote:
> Hi Fu-Ming,
>
> Looks similar to this bug:
>
> http://issues.apache.org/jira/browse/HDFS-686
>
> Does this problem persist, or was it a one time occurrence?
>
> -Todd
>
>
> On Tue, Dec 15, 2009 at 5:42 PM, Fu-Ming Tsai <sa...@gmail.com> wrote:
>
>> Hello, all,
>>
>> I tried to execute 2 SecondaryNamenode in my env. However, one worked
>> fine but the other one failed.
>> From the log file, I found the following message.
>>
>> 2009-12-15 15:25:19,429 ERROR
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: Throwable
>> Exception in doCheckpoint:
>> 2009-12-15 15:25:19,430 ERROR
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode:
>> java.lang.NullPointerException
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1006)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:992)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:966)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:953)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:696)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:992)
>> at
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.doMerge(SecondaryNameNode.java:590)
>> at
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.access$000(SecondaryNameNode.java:473)
>> at
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doMerge(SecondaryNameNode.java:350)
>> at
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:314)
>> at
>> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.run(SecondaryNameNode.java:225)
>> at java.lang.Thread.run(Thread.java:619)
>>
>> I'm not sure what it happened. Did anyone encounter this problem before??
>>
>>
>>
>> Best regards,
>> Fu-Ming
>>
>
--
------------------------------------
"Losers always whine about their best."
Fu-Ming Tsai
sary357@gmail.com
------------------------------------
Re: error message when executing SecondaryNameNode
Posted by Todd Lipcon <to...@cloudera.com>.
Hi Fu-Ming,
Looks similar to this bug:
http://issues.apache.org/jira/browse/HDFS-686
Does this problem persist, or was it a one time occurrence?
-Todd
On Tue, Dec 15, 2009 at 5:42 PM, Fu-Ming Tsai <sa...@gmail.com> wrote:
> Hello, all,
>
> I tried to execute 2 SecondaryNamenode in my env. However, one worked
> fine but the other one failed.
> From the log file, I found the following message.
>
> 2009-12-15 15:25:19,429 ERROR
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: Throwable
> Exception in doCheckpoint:
> 2009-12-15 15:25:19,430 ERROR
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode:
> java.lang.NullPointerException
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:1006)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.addChild(FSDirectory.java:992)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:966)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.unprotectedMkdir(FSDirectory.java:953)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(FSEditLog.java:696)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(FSImage.java:992)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.doMerge(SecondaryNameNode.java:590)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.access$000(SecondaryNameNode.java:473)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doMerge(SecondaryNameNode.java:350)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:314)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.run(SecondaryNameNode.java:225)
> at java.lang.Thread.run(Thread.java:619)
>
> I'm not sure what it happened. Did anyone encounter this problem before??
>
>
>
> Best regards,
> Fu-Ming
>