[
https://issues.apache.org/jira/browse/HDFS-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HDFS-4201:
------------------------------
Attachment: trunk-4201.patch
Attached a patch that fixed datanode initBlockPool error handling. With this
fix, if BPOfferService fails to connect to one NN, it still can connect other
NNs, if any, without throwing NPE.
> 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
> Attachments: trunk-4201.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)
