[
https://issues.apache.org/jira/browse/PIG-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575869#comment-13575869
]
Koji Noguchi commented on PIG-3178:
-----------------------------------
bq. Doesn't LOG.error(t); log the stacktrace?
I thought it only prints out the cause. After adding the printStackTrace call,
log showed
{noformat}
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2271)
at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:113)
at
java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:122)
at org.apache.pig.builtin.PigStreaming.serialize(PigStreaming.java:76)
at org.apache.pig.impl.streaming.InputHandler.putNext(InputHandler.java:66)
at
org.apache.pig.impl.streaming.ExecutableManager$ProcessInputThread.run(ExecutableManager.java:367)
{noformat}
which helped me identify the killer record filling up the heap.
> Print a stacktrace when ExecutableManager hits an OOM
> -----------------------------------------------------
>
> Key: PIG-3178
> URL: https://issues.apache.org/jira/browse/PIG-3178
> Project: Pig
> Issue Type: Improvement
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Priority: Trivial
> Attachments: pig-3178-trunk-v01.patch
>
>
> When looking at user's pig streaming failing with OOM, it only showed
> 2013-02-09 03:35:08,694 ERROR [Thread-14]
> org.apache.pig.impl.streaming.ExecutableManager: java.lang.OutOfMemoryError:
> Java heap space
> It would have been nice if it also showed the stack trace.
--
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
