[
https://issues.apache.org/jira/browse/PIG-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated PIG-1838:
----------------------------------
Description: We're starting to see issues where interactive/command line
pig users blow up due to so many large jar creations in /tmp. (In other words,
pig execution prior to the java.io.tmpdir fix that Hadoop makes can kick in.)
Pig should probably not depend upon users being savvy enough to override
java.io.tmpdir on their own in these situations and/or a better steward of the
space it does use. (was: We're starting to issues where interactive/command
line pig users blow up due to so many large jar creations in /tmp. (In other
words, pig execution prior to the java.io.tmpdir fix that Hadoop makes can kick
in.) Pig should probably not depend upon users being savvy enough to override
java.io.tmpdir on their own in these situations and/or a better steward of the
space it does use. )
> On a large farm, some pigs die of /tmp starvation
> -------------------------------------------------
>
> Key: PIG-1838
> URL: https://issues.apache.org/jira/browse/PIG-1838
> Project: Pig
> Issue Type: Wish
> Components: impl
> Affects Versions: 0.8.0
> Reporter: Allen Wittenauer
>
> We're starting to see issues where interactive/command line pig users blow up
> due to so many large jar creations in /tmp. (In other words, pig execution
> prior to the java.io.tmpdir fix that Hadoop makes can kick in.) Pig should
> probably not depend upon users being savvy enough to override java.io.tmpdir
> on their own in these situations and/or a better steward of the space it does
> use.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
