You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/05/08 19:45:02 UTC

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

Chris Nauroth created ZOOKEEPER-2185:
----------------------------------------

             Summary: 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)