[jira] [Commented] (ZOOKEEPER-2185) Document recommendation to use -XX:HeapDumpOnOutOfMemoryError and -XX:OnOutOfMemoryError="kill %p" for server.

["Chris Nauroth (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535063#comment-14535063 ] 

Chris Nauroth commented on ZOOKEEPER-2185:
------------------------------------------

This suggestion came up on the dev mailing list:

http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201505.mbox/%3CCANLc_9LL8PaJ-UMmrENgpyEWYsB8F8s2uySuCnYajUan6EO2Jw%40mail.gmail.com%3E

> Document recommendation to use -XX:HeapDumpOnOutOfMemoryError and -XX:OnOutOfMemoryError="kill %p" for server.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2185
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2185
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>
> Continuing to run a server process after it runs out of memory can lead to unexpected behavior.  This issue proposes that we update documentation to recommend adding these JVM options:
> # {{-XX:HeapDumpOnOutOfMemoryError}} for help with post-mortem analysis of why the process ran out of memory.
> # {{-XX:OnOutOfMemoryError="kill %p"}} to kill the JVM process, under the assumption that a process monitor will restart it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)