[
https://issues.apache.org/jira/browse/ZOOKEEPER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt reassigned ZOOKEEPER-1991:
---------------------------------------
Assignee: Reed Wanderman-Milne
Reed you want to give this a try? (patch I mean). Thanks.
> zkServer.sh returns with a zero exit status when a ZooKeeper process is
> already running
> ---------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1991
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1991
> Project: ZooKeeper
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.4.6
> Reporter: Reed Wanderman-Milne
> Assignee: Reed Wanderman-Milne
> Priority: Minor
> Fix For: 3.4.7, 3.5.0
>
>
> If ZooKeeper is started with zkServer.sh, and an error is shown that a
> ZooKeeper process is already running, the command returns with an exit status
> of 0, while it should end with a non-zero exit status.
> Example:
> $ bin/zkServer.sh start
> JMX enabled by default
> Using config: /home/reed/zookeeper/bin/../conf/zoo.cfg
> Starting zookeeper ... already running as process 25063.
> $ echo $?
> 0
> This can make it difficult for automated scripts to check if creating a new
> ZooKeeper process was successful, as it won't catch if a user accidentally
> started it before.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
