[ 
https://issues.apache.org/jira/browse/HDFS-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273052#comment-13273052
 ] 

Todd Lipcon commented on HDFS-3391:
-----------------------------------

I was able to reproduce this by reapplying HDFS-3157 and adding the following 
in DataNode.java:

{code}
--- 
a/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
+++ 
b/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
@@ -1983,6 +1983,13 @@ public class DataNode extends Configured
       datanodes[i] = r.id;
       storages[i] = r.storageID;
     }
+    if (newBlock.getGenerationStamp() == 1005) {
+      try {
+        Thread.sleep(1500);
+      } catch (InterruptedException ie) {
+        Thread.currentThread().interrupt();
+      }
+    }
     nn.commitBlockSynchronization(block,
         newBlock.getGenerationStamp(), newBlock.getNumBytes(), true, false,
         datanodes, storages);
{code}

I have to think through whether this is a bug which we've had for a while which 
is uncovered by HDFS-3157, or if HDFS-3157 itself was incorrect.
                
> TestPipelinesFailover#testLeaseRecoveryAfterFailover is failing
> ---------------------------------------------------------------
>
>                 Key: HDFS-3391
>                 URL: https://issues.apache.org/jira/browse/HDFS-3391
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Arun C Murthy
>            Assignee: Todd Lipcon
>            Priority: Critical
>
> Running org.apache.hadoop.hdfs.server.blockmanagement.TestRBWBlockInvalidation
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.208 sec <<< 
> FAILURE!
> --
> Running org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
> Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 81.195 sec 
> <<< FAILURE!
> --

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to