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

Hadoop QA commented on HADOOP-8158:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12538168/HADOOP-8158.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test 
files.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed unit tests in 
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1224//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/1224//console

This message is automatically generated.
                
> 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, 2.0.0-alpha, 3.0.0
>            Reporter: Todd Lipcon
>            Assignee: Daryn Sharp
>         Attachments: 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: 
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