Hadoop QA commented on ZOOKEEPER-485:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 912052.

    +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 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: 
Findbugs warnings: 
Console output: 

This message is automatically generated.

> need ops documentation that details supervision of ZK server processes
> ----------------------------------------------------------------------
>                 Key: ZOOKEEPER-485
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-485
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: documentation, server
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>             Fix For: 3.3.0
>         Attachments: ZOOKEEPER-485.patch
> We need ops documentation detailing what to do if the ZK server VM fails - by 
> fail I mean the jvm process
> exits/dies/crashes/etc...
> In general a supervisor process should be used to start/stop/restart/etc... 
> the ZK server vm.
> Something like daemontools http://cr.yp.to/daemontools.html could be used, or 
> more simply a wrapper script
> should monitor the status of the pid and restart if the jvm fails. It's up to 
> the operator, if this is not done
> automatically then it will have to be done manually, by operator restarting 
> the ZK server jvm
> The inherent behavior of ZK wrt to failures - ie that it automatically 
> recovers as long as quorum is maintained - 
> fits into this nicely.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to