[ 
https://issues.apache.org/jira/browse/HDFS-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842102#comment-13842102
 ] 

Hadoop QA commented on HDFS-4201:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12617539/trunk-4201_v2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-hdfs-project/hadoop-hdfs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/5672//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5672//console

This message is automatically generated.

> NPE in BPServiceActor#sendHeartBeat
> -----------------------------------
>
>                 Key: HDFS-4201
>                 URL: https://issues.apache.org/jira/browse/HDFS-4201
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>            Reporter: Eli Collins
>            Assignee: Jimmy Xiang
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: trunk-4201.patch, trunk-4201_v2.patch
>
>
> Saw the following NPE in a log.
> Think this is likely due to {{dn}} or {{dn.getFSDataset()}} being null, (not 
> {{bpRegistration}}) due to a configuration or local directory failure.
> {code}
> 2012-09-25 04:33:20,782 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: 
> For namenode svsrs00127/11.164.162.226:8020 using DELETEREPORT_INTERVAL of 
> 300000 msec  BLOCKREPORT_INTERVAL of 21600000msec Initial delay: 0msec; 
> heartBeatInterval=3000
> 2012-09-25 04:33:20,782 ERROR 
> org.apache.hadoop.hdfs.server.datanode.DataNode: Exception in BPOfferService 
> for Block pool BP-1678908700-11.164.162.226-1342785481826 (storage id 
> DS-1031100678-11.164.162.251-5010-1341933415989) service to 
> svsrs00127/11.164.162.226:8020
> java.lang.NullPointerException
>         at 
> org.apache.hadoop.hdfs.server.datanode.BPServiceActor.sendHeartBeat(BPServiceActor.java:434)
>         at 
> org.apache.hadoop.hdfs.server.datanode.BPServiceActor.offerService(BPServiceActor.java:520)
>         at 
> org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:673)
>         at java.lang.Thread.run(Thread.java:722)
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to