[
https://issues.apache.org/jira/browse/SAMZA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137551#comment-14137551
]
Chris Riccomini commented on SAMZA-414:
---------------------------------------
bq. Putting the dump to ./tmp or $SAMZA_LOG_DIR causes problems. Seems so far
the /tmp is the only option we have.
Yea, I can't see another way around this. I was thinking maybe we could do the
heap dump in an ascii (non-binary) format, but it sounds like the JVM doesn't
support this.
bq. Some tools, such as jvisualvm shipped with Java, will dump the heapDump to
the /tmp anyway when the users debug. I was thinking it was fine that we dump
to the /tmp as well.
I think VisualVM defaults to /tmp, but it always asks before it does it, and
gives you an opportunity to change it.
bq. Maybe we should give a caveat to the users and make this optional ?
Yea. If so we basically don't need this feature. It's already optional simply
by having the user set task.opts with the heap dump switches they need.
It's too bad. It does seem like this would be a handy feature to have on by
default. Maybe I'm just over-thinking things, though.
> 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)
