Thanks for your replay.
I can see that the pid the runit save, is deferent from the pid that I
acctually have running on the machine , could it be that the launcher of
the kafka broker forks another process with a different PID?
The only way I could kill the process is by using kill -9 , I suspect
that runit doesn't use the
On 07/05/2012 10:19 PM, Jay Kreps wrote:
> I think what you are saying is that you don't have the process id for the
> broker so you don't have the right thing to kill?
> Two solutions I know:
> 1. Change your script to store the process id somewhere, and use that for
> the kill
> 2. Use pkill and just kill all kafka instances (only works if there is only
> one broker per node)
> On Thu, Jul 5, 2012 at 2:24 AM, Guy Doulberg <[EMAIL PROTECTED]>wrote:
>> Hi guys,
>> In my deployment of Kafka I am using runit to control the service of the
>> kafka broker.
>> In the run script I have this line:
>> exec 2>&1
>> exec /opt/kafka/bin/kafka-server-**start.sh /etc/kafka/server.properties
>> It works fine, if I want to start the broker, but if I want to stop or
>> restart the process, the kafka broker doesn't get kill...
>> So eventually the old kafka broker prevents from the new broker to start
>> (Because the ports are already binded).
>> Of course the running the same line of code in the shell and then ctrl-c
>> ing works good (as you know kafka broker is not a daemon)
>> I was wondering if someone has encountered this phenomena and solved it.
>> Guy Doulberg