[ https://issues.apache.org/jira/browse/HDFS-8827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654707#comment-14654707 ]
Takuya Fukudome commented on HDFS-8827: --------------------------------------- Could you check surefire-reports log files which mvn test generated? I have ran command {{mvn test -Dtest=org.apache.hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks}} and I found the NPE in {{hadoop-hdfs/target/surefire-reports/org.apache.hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks-output.txt}}. If there is a better way to write this test, please let me know. Thank you. > Erasure Coding: When namenode processes over replicated striped block, NPE > will be occur in ReplicationMonitor > -------------------------------------------------------------------------------------------------------------- > > Key: HDFS-8827 > URL: https://issues.apache.org/jira/browse/HDFS-8827 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Takuya Fukudome > Assignee: Takuya Fukudome > Attachments: HDFS-8827.1.patch, processing-over-replica-npe.log > > > In our test cluster, when namenode processed over replicated striped blocks, > null pointer exception(NPE) occurred. This happened under below situation: 1) > some datanodes shutdown. 2) namenode recovers block group which lost internal > blocks. 3) restart the stopped datanodes. 4) namenode processes over > replicated striped blocks. 5) NPE occurs > I think BlockPlacementPolicyDefault#chooseReplicaToDelete will return null in > this situation which causes this NPE problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)