[HDFS-4201] NPE in BPServiceActor#sendHeartBeat

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.3.0
• Component/s: namenode
• Target Version/s: 2.3.0
• Assignee: Jimmy Xiang
• Reporter: Eli Collins
• Created: 16/Nov/12 21:28
• Updated: 24/Feb/14 20:58
• Resolved: 11/Dec/13 21:30

Description

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.

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)

Issue Links

• is duplicated by: HDFS-4442 Initialization failed for block (...) Invalid volume failure config value: 1
• relates to: HDFS-2882 DN continues to start up, even if block pool fails to initialize