You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Stefan Groschupf (JIRA)" <ji...@apache.org> on 2008/02/27 21:41:56 UTC

[jira] Commented: (PIG-99) Tests: OutOfMemoryError: Java heap space

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

Stefan Groschupf commented on PIG-99:
-------------------------------------

Hi Benjamin, 
Sorry I missed your memory settings in the new build.xml. I actually did not see any OOM problems running the test suite before without those parameters.
All tests run through with the 64MB standard jvm memory. 
If that is not the case I guess we have a memory leak since hadoop as pig should use streaming as much as possible. 
I hadn't the chance to look into the pig memory management yet. However from browsing the code I guess it shouldn't matter how much memory you have. 
If that is not the case than you find a bug and we should investigate. 


> Tests: OutOfMemoryError: Java heap space
> ----------------------------------------
>
>                 Key: PIG-99
>                 URL: https://issues.apache.org/jira/browse/PIG-99
>             Project: Pig
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 0.1.0
>            Reporter: Benjamin Francisoud
>             Fix For: 0.1.0
>
>         Attachments: PIG-99-v01.patch, PIG-99-v02.patch, PIG-99-v03.patch
>
>
> While running tests:
> {noformat}
>     [junit] Testcase: testAVG took 0,11 sec
>     [junit] Testcase: testAVGInitial took 0 sec
>     [junit] Testcase: testAVGFinal took 0 sec
>     [junit] Testcase: testCOUNT took 0 sec
>     [junit] Testcase: testCOUNTMap took 0 sec
>     [junit] Testcase: testCOUNTInitial took 0 sec
>     [junit] Testcase: testCOUNTFinal took 0 sec
>     [junit] Testcase: testSUM took 0 sec
>     [junit] Testcase: testSUMInitial took 0 sec
>     [junit] Testcase: testSUMFinal took 0 sec
>     [junit] Testcase: testMIN took 0 sec
>     [junit] Testcase: testMINInitial took 0 sec
>     [junit] Testcase: testMINFinal took 0 sec
>     [junit] Testcase: testMAX took 0 sec
>     [junit] Testcase: testMAXInitial took 0 sec
>     [junit] Testcase: testMAXFinal took 0 sec
>     [junit] Testcase: testLFPig took 0,953 sec
>     [junit] 	Caused an ERROR
>     [junit] Java heap space
>     [junit] java.lang.OutOfMemoryError: Java heap space
>     [junit] 
> {noformat}
> Proposed patch, add this to the junit tag:
> {code:xml}<jvmarg value="-Xmx512m  -XX:PermSize=128m -XX:MaxPermSize=512m"/>{code}
> or
> {code:xml}
> <jvmarg value="-Xmx512m"/>
> <jvmarg value="-XX:PermSize=128m"/>
> <jvmarg value="-XX:MaxPermSize=512m"/>
> {code}
> not sure which one is correct, I need to check...
> See [JUnit task|http://ant.apache.org/manual/OptionalTasks/junit.html] for more details
> An *even better solution* is to check why there is a OutOfMemoryError in the first place.
> May be it's a sign somethings'wrong or consuming too much memory...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.