[
https://issues.apache.org/jira/browse/SAMZA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136174#comment-14136174
]
Chris Riccomini commented on SAMZA-414:
---------------------------------------
I *think* that the heap dump should be moved to HDFS. Since the OOM triggers
the heap dump, and the heap dump happens before the PID disappears, and the PID
disappears before the log aggregation is run, I think this means that YARN
should put the heap dump in HDFS.
That said, I can't test it, as I'm not running HDFS.
> Enable HeapDumpOnOutOfMemoryError by default
> --------------------------------------------
>
> Key: SAMZA-414
> URL: https://issues.apache.org/jira/browse/SAMZA-414
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.8.0
> Reporter: Chris Riccomini
> Assignee: Chris Riccomini
> Fix For: 0.8.0
>
> Attachments: SAMZA-414-0.patch, SAMZA-414-1.patch, log-hprof.png
>
>
> It would be nice if Samza's run-class.sh defaulted to use
> -XX:+HeapDumpOnOutOfMemoryError. According to
> [this|http://stackoverflow.com/questions/542979/using-heapdumponoutofmemoryerror-parameter-for-heap-dump-for-jboss]
> post, it puts the heap dump in CWD by default, which should be fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
