[ https://issues.apache.org/jira/browse/HDFS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480535#comment-13480535 ]
Jing Zhao commented on HDFS-4067: --------------------------------- And I guess that's also the reason for HDFS-342? Since the initial replication request is ignored, the replication on D1 can only be done after the pending replication timeout. > TestUnderReplicatedBlocks may fail due to ReplicaAlreadyExistsException > ----------------------------------------------------------------------- > > Key: HDFS-4067 > URL: https://issues.apache.org/jira/browse/HDFS-4067 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.0.0-alpha > Reporter: Eli Collins > Assignee: Jing Zhao > Labels: test-fail > > After adding the timeout to TestUnderReplicatedBlocks in HDFS-4061 we can see > the root cause of the failure is ReplicaAlreadyExistsException: > {noformat} > org.apache.hadoop.hdfs.server.datanode.ReplicaAlreadyExistsException: Block > BP-1541130889-172.29.121.238-1350435573411:blk_-3437032108997618258_1002 > already exists in state FINALIZED and thus cannot be created. > at > org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl.createTemporary(FsDatasetImpl.java:799) > at > org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl.createTemporary(FsDatasetImpl.java:90) > at > org.apache.hadoop.hdfs.server.datanode.BlockReceiver.<init>(BlockReceiver.java:155) > at > org.apache.hadoop.hdfs.server.datanode.DataXceiver.writeBlock(DataXceiver.java:393) > at > org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.opWriteBlock(Receiver.java:98) > at > org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.processOp(Receiver.java:66) > at > org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:219) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira