You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Olga Natkovich (JIRA)" <ji...@apache.org> on 2009/10/06 02:47:31 UTC
[jira] Updated: (PIG-975) Need a databag that does not register
with SpillableMemoryManager and spill data pro-actively
[ https://issues.apache.org/jira/browse/PIG-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Natkovich updated PIG-975:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
patch committed. Thanks, Ying
> Need a databag that does not register with SpillableMemoryManager and spill data pro-actively
> ---------------------------------------------------------------------------------------------
>
> Key: PIG-975
> URL: https://issues.apache.org/jira/browse/PIG-975
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.4.0
> Reporter: Ying He
> Assignee: Ying He
> Fix For: 0.6.0
>
> Attachments: internalbag.xls, PIG-975.patch, PIG-975.patch2, PIG-975.patch3, PIG-975.patch4
>
>
> POPackage uses DefaultDataBag during reduce process to hold data. It is registered with SpillableMemoryManager and prone to OutOfMemoryException. It's better to pro-actively managers the usage of the memory. The bag fills in memory to a specified amount, and dump the rest the disk. The amount of memory to hold tuples is configurable. This can avoid out of memory error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.