[
https://issues.apache.org/jira/browse/SAMZA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137502#comment-14137502
]
Chris Riccomini commented on SAMZA-414:
---------------------------------------
bq. Though the explanation is a little long, the solution is simple, we can put
them into "/tmp".
Oops, missed that you were using root /tmp, not the ./tmp in the CWD, which is
what run-class.sh was doing in the first patch. The problem that I have with
putting the dump in /tmp is that /tmp is a shared resource, and is usually not
monitored all that well. The dumps can easily get to be 500+ megs. This could
very easily fill /tmp space, which will break a lot of things.
> 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)
