ZooKeeper
  1. ZooKeeper
  2. ZOOKEEPER-1991

zkServer.sh returns with a zero exit status when a ZooKeeper process is already running

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.4.6
    • Fix Version/s: 3.5.2, 3.6.0
    • Component/s: scripts
    • Labels:
      None

      Description

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Reed Wanderman-Milne
            Reporter:
            Reed Wanderman-Milne
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development