Hello,

I recently started using the 0.10.2.1 distro on Ubuntu Linux and trying
some basic startup for a 3 node cluster (using the setup mentioned in the
documentation).

The following is a custom startup that I have written (I have also tried
this by calling them individually in the same order):


#!/bin/bash
(sh ./zookeeper-server-start.sh ../config/zookeeper.properties) &
read -t 5 -p "Please wait.........." || true
(sh ./zookeeper-server-start.sh ../config/zookeeper2.properties) &
read -t 5 -p "Please wait.........." || true
(sh ./zookeeper-server-start.sh ../config/zookeeper3.properties) &
read -t 5 -p "Please wait.........." || true
(sh ./kafka-server-start.sh ../config/server.properties) &
read -t 5 -p "Please wait.........." || true
(sh ./kafka-server-start.sh ../config/server2.properties) &
read -t 5 -p "Please wait.........." || true
(sh ./kafka-server-start.sh ../config/server3.properties) &


p.s. the read statement doesn't do anything - it gives a few seconds to
settle down.

When I call the server-stop scripts. Only zookeeper is shutdown, Kafka
always hangs. I understand that we are doing a KILL 15 which is terminate
for all the items. But when I do the following after I shutdown everything:

ps ax | grep java | grep -i "kafka.\Kafka" | awk '{print $1}'

I can still see kafka brokers running - even when I called a SIGTERM on
them.

Do I need to modify the server-stop scripts in a specific way? Is this
expected? I know that the best use to use probably start it as a daemon -
but I was hoping that this simple setup should work normally.

Any ideas?

Reply via email to