[
https://issues.apache.org/jira/browse/IMPALA-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020578#comment-17020578
]
Tim Armstrong commented on IMPALA-1956:
---------------------------------------
At the moment this is left to whatever is managing Impala - I've seen a bunch
of deployments that do this successfully. I think we can probably do a few
things here:
* Update docs to recommend setting this
* Investigate if there's a way to enable this by default for the embedded JVM
(I guess overridable by JAVA_TOOL_OPTIONS though...)
* Set this for our end-to-end tests.
> impala components with embedded JVM should exit, produce heap dump on OOM
> -------------------------------------------------------------------------
>
> Key: IMPALA-1956
> URL: https://issues.apache.org/jira/browse/IMPALA-1956
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 2.1.1, Impala 2.2
> Reporter: Chris Leroy
> Assignee: Juan Yu
> Priority: Minor
> Labels: ramp-up, supportability
>
> I believe a number of Impala components embed a JVM. If an OOM occurs in java
> code running in that JVM, it would be nice if a heap dump was produced and
> the Impala component could be configured to exit. Basically if we could have
> the equivalent of "-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp
> -XX:OnOutOfMemoryError=kill -9 %p". This is on the presumption that the OOM
> leaves the JVM in particular and the Impala component in general in an
> unusable state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
