Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Sat, 21 Jul 2012 08:43:34 +0000 (UTC)
From: "Haitao Yao (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <370593219.85615.1342860214567.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <101488258.34381.1341999754762.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (PIG-2812) Spill InternalCachedBag into only 1
 file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Haitao Yao commented on PIG-2812:
---------------------------------

well, the spilled files should have been cleared under the normal condition. But if your job failed, and the Tasktracker reuses the child java process, the OOM would happen.
I really think spill to one file is better.

                
> Spill InternalCachedBag into only 1 file
> ----------------------------------------
>
>                 Key: PIG-2812
>                 URL: https://issues.apache.org/jira/browse/PIG-2812
>             Project: Pig
>          Issue Type: Bug
>          Components: data
>            Reporter: Haitao Yao
>             Fix For: 0.11
>
>         Attachments: aa.jpg
>
>
> I encountered a reducer's OOM because of java.io.DeleteOnExitHook. And I found out that the InternalCachedBag creates a seperate tmp file, and the tmp files is deleted on exit. So the file delete hook caused the OOM. 
> Why not just hold the tmp file handle and spill only one tmp file?
> Too many tmp files may block the tasktracker start process, if the tmp files are not cleaned on time and the tasktracker restarts at this specific time.

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