Hi William, do you have staging/running/failed/killed broker tasks? First thought looking at the status the issue could be that you have the heap == mem, when setting it so small for testing usually twice the size (assuming you have cgroups for your isolator). What version are you using?
~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - - On Thu, Jun 4, 2015 at 5:38 PM, William Francis <[email protected]> wrote: > > Hello - I have Mesos and Marathon running on centos 7. I'm trying to get > Kafka running but am having difficulty starting the brokers. I can launch > the scheduler directly as a framework or as a docker container and that is > fine (I think) but when I try to launch the brokers they time out and I'm > not aware of any logs I can look through to find out what's going on. > > In this example I start up a kafa-mesos docker container on my slave2 and > then attempt to control it from master1. > > This is all with java 1.7.0 > > docker run -it -p 7000:7000 --add-host=master1:172.27.1.11 > root/kafka-mesos ./kafka-mesos.sh scheduler --master=master1:5050 > --zk=master1:2181 --api=http://172.27.2.12:7000 > --storage=file:kafka-mesos.json > > 2015-06-04 20:46:04,664 [main] INFO ly.stealth.mesos.kafka.Scheduler$ - > Starting Scheduler$: > debug: false, storage: file:kafka-mesos.json > mesos: master=master1:5050, user=<default>, principal=<none>, secret=<none> > framework: name=kafka, role=*, timeout=30d > api: http://172.27.2.12:7000, zk: master1:2181, jre: <none> > 2015-06-04 20:46:04,780 [main] INFO org.eclipse.jetty.server.Server - > jetty-9.0.z-SNAPSHOTWrappedArray() > 2015-06-04 20:46:04,821 [main] INFO > org.eclipse.jetty.server.handler.ContextHandler - Started > WrappedArray(o.e.j.s.ServletContextHandler@13a15f06{/,null,AVAILABLE}) > 2015-06-04 20:46:04,850 [main] INFO > org.eclipse.jetty.server.ServerConnector - Started > WrappedArray(ServerConnector@2f37e8bc{HTTP/1.1}{0.0.0.0:7000}) > 2015-06-04 20:46:04,851 [main] INFO ly.stealth.mesos.kafka.HttpServer$ - > started on port 7000 > I0604 20:46:04.943804 16 sched.cpp:157] Version: 0.22.1 > I0604 20:46:04.947131 43 sched.cpp:254] New master detected at > [email protected]:5050 > I0604 20:46:04.947571 43 sched.cpp:264] No credentials provided. > Attempting to register without authentication > > then back on my master1: > > [root@wfrancis-centos7-master1 kafka]# ./kafka-mesos.sh status --api= > http://slave2:7000 > Cluster status received > > cluster: > brokers: > > [root@wfrancis-centos7-master1 kafka]# ./kafka-mesos.sh add 0 --api= > http://slave2:7000 > Broker added > > broker: > id: 0 > active: false > state: stopped > resources: cpus:0.50, mem:128, heap:128 > failover: delay:10s, max-delay:60s > > [root@wfrancis-centos7-master1 kafka]# ./kafka-mesos.sh start 0 --api= > http://slave2:7000 > Error: Broker 0 scheduled to start. Got timeout > > [root@wfrancis-centos7-master1 kafka]# ./kafka-mesos.sh status --api= > http://slave2:7000 > Cluster status received > > cluster: > brokers: > id: 0 > active: true > state: starting > resources: cpus:0.50, mem:128, heap:128 > failover: delay:10s, max-delay:60s > > However the broker never starts. Ideas of how to debug this? > > >
