You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2012/10/19 10:40:14 UTC

[jira] [Moved] (MAPREDUCE-4737) Hadoop does not close output file / does not call Mapper.cleanup if exception in map

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Srinivas moved HADOOP-8904 to MAPREDUCE-4737:
----------------------------------------------------

             Assignee:     (was: Daniel Dai)
    Affects Version/s:     (was: 1-win)
                       1-win
                  Key: MAPREDUCE-4737  (was: HADOOP-8904)
              Project: Hadoop Map/Reduce  (was: Hadoop Common)
    
>  Hadoop does not close output file / does not call Mapper.cleanup if exception in map
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4737
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4737
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1-win
>            Reporter: Daniel Dai
>         Attachments: HADOOP-23-2.patch, HADOOP-8904-1.patch
>
>
> Find this in Pig unit test TestStore under Windows. There are dangling files because map does not close the file when exception happens in map(). In Windows, Hadoop will not remove a file if it is not closed. This happens in reduce() as well.

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