mesos/kafka

Unable to add brokers when zk and storage options have chroot

Closed this issue · 3 comments

mindscratch commented

I've got the 0.9.4.0 scheduler running with the following kafka-mesos.properties file:

storage=zk:/kafka-mesos-0.9.4.0
master=zk://server1:2181/mesos
zk=server1:2181/kafka09

note: I'm trying to get to the point where I run the 0.9.2.0 framework with its own brokers as well as the 0.9.4.0 framework with its own brokers, hence the chroot in the zk option and the different storage path.

Anyhow, so far, just the 0.9.4.0 scheduler is up. In zookeeper I now have /kafka09/mesos. I try to add a broker, I see /kafka09/kafka-mesos-0.9.4.0 show up. In the terminal where I issued the ./kafka-mesos.sh broker add ... I get:

brokers added:
# output about the broker here

I then try to start the broker with:

> kafka-mesos.sh broker start 0 --api http://<host running kafka framework>:<port>
Error: brokers start timeout

Any thoughts?

mindscratch commented

This might be because I have the kafka-mesos-0.9.2.0.jar in the directory where i'm running kafka-mesos.sh, instead of 0.9.4.0, I'll report bac.

mindscratch commented

Ok, I put replaced the kafka-mesos jar so it's the kafka-mesos-0.9.4.0.jar.

I tried starting the broker again and still got the Error: brokers start timeout

If I execute: ./kafka-mesos.sh broker list --api http://<host running kafka framework>:<port> and I get the list showing my broker as active: true and state: starting.

mindscratch commented

It was my own problem. The actual kafka-mesos.properties that was generated (I'm using puppet) looked like this (because of a variable being reused in a template):

storage=zk:/kafka-mesos-0.9.4.0
master=zk://server1:2181/kafka09/mesos
zk=server1:2181/kafka09

The master option was incorrect!