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

Hadoop QA commented on ZOOKEEPER-2185:
--------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12734261/ZOOKEEPER-2185.001.patch
  against trunk revision 1680471.

    +1 @author.  The patch does not contain any @author tags.

    +0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 2.0.3) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2706//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2706//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2706//console

This message is automatically generated.

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

Reply via email to