hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8633) Interrupted FsShell copies may leave tmp files
Date Thu, 02 Aug 2012 14:05:05 GMT

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

Hudson commented on HADOOP-8633:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #1155 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1155/])
    HADOOP-8633. Interrupted FsShell copies may leave tmp files (Daryn Sharp via tgraves)
(Revision 1368002)

     Result = FAILURE
tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1368002
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/shell/CommandWithDestination.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/shell/PathData.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/shell/TestCopy.java

                
> Interrupted FsShell copies may leave tmp files
> ----------------------------------------------
>
>                 Key: HADOOP-8633
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8633
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>             Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>
>         Attachments: HADOOP-8633.patch
>
>
> Interrupting a copy, ex. via SIGINT, may cause tmp files to not be removed.  If the user
is copying large files then the remnants will eat into the user's quota.

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

        

Mime
View raw message