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/21 00:51:59 UTC

[jira] [Updated] (ZOOKEEPER-2185) Run server with -XX:+HeapDumpOnOutOfMemoryError and -XX:OnOutOfMemoryError='kill %p'.

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated ZOOKEEPER-2185:
-------------------------------------
    Description: 
Continuing to run a server process after it runs out of memory can lead to unexpected behavior.  This issue proposes that we update scripts and documentation to add 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.

  was:
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.


> Run server with -XX:+HeapDumpOnOutOfMemoryError and -XX:OnOutOfMemoryError='kill %p'.
> -------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2185
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2185
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: documentation, scripts
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: ZOOKEEPER-2185.001.patch
>
>
> Continuing to run a server process after it runs out of memory can lead to unexpected behavior.  This issue proposes that we update scripts and documentation to add 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)