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

Hudson commented on HADOOP-8158:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #2758 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2758/])
    HADOOP-8158. Interrupting hadoop fs -put from the command line causes a 
LeaseExpiredException. Contributed by Daryn Sharp. (harsh) (Revision 1389010)

     Result = SUCCESS
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1389010
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DistributedFileSystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDistributedFileSystem.java

                
> Interrupting hadoop fs -put from the command line causes a 
> LeaseExpiredException
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-8158
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8158
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Daryn Sharp
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-8158.patch, HADOOP-8158.patch
>
>
> If you run "hadoop fs -put - foo", write a few lines, then ^C it from the 
> shell, about half the time you will get a LeaseExpiredException. It seems 
> like the shell is first calling {{delete()}} on the file, then calling 
> {{close()}} on the stream. The {{close}} call fails since the {{delete}} call 
> kills the lease. I saw this on trunk but my guess is that it affects 23 also.

--
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

Reply via email to