Details
Description
Active NamNode exit due to NPE, I can confirm that the BlockCollection passed in when creating ReplicationWork is null, but I do not know why BlockCollection is null, By view history I found HDFS-9754 remove judging whether BlockCollection is null.
NN logs are as following:
2017-10-11 16:29:06,161 ERROR [ReplicationMonitor] org.apache.hadoop.hdfs.server.blockmanagement.BlockManager: ReplicationMonitor thread received Runtime exception. java.lang.NullPointerException at org.apache.hadoop.hdfs.server.blockmanagement.ReplicationWork.chooseTargets(ReplicationWork.java:55) at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeReplicationWorkForBlocks(BlockManager.java:1532) at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeReplicationWork(BlockManager.java:1491) at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeDatanodeWork(BlockManager.java:3792) at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager$ReplicationMonitor.run(BlockManager.java:3744) at java.lang.Thread.run(Thread.java:834)
Attachments
Attachments
Issue Links
- is broken by
-
HDFS-9754 Avoid unnecessary getBlockCollection calls in BlockManager
- Resolved
- is related to
-
HDFS-7056 Snapshot support for truncate
- Closed
-
HDFS-8330 BlockInfoContiguous in blocksMap can have null BlockCollection
- Open
-
HDFS-12880 Disallow abandoned blocks in the BlocksMap
- Open
- relates to
-
HDFS-13027 Handle possible NPEs due to deleted blocks in race condition
- Resolved
-
HDFS-12884 BlockUnderConstructionFeature.truncateBlock should be of type BlockInfo
- Resolved