ror6ax

Hi @shervinea , this is finally done ;)

@grendach - care to review this one?

Hi guys, what is the status? Will you agree to merge when conflicts are resolved?

@containersol @nubunto - guys, can we please get the update on this?

In fact, only entry in the logs apart from ACCEPTs and immediate DECLINEs is happening when I re-start the broker. Neither clients nor master sow anything related to Kafka in...

I have switched to Marathon scheduler. Logs are a bit more verbose now. Broker start fails with ``` 2017-03-14 15:04:09,148 INFO BrokerLifecycleManager] Broker 0 failed 2, waiting 2m, next start...

I've substituded --api to Mesos-DNS provided name, got one step closer: ``` 2017-03-14 15:14:45,877 INFO KafkaMesosScheduler] [statusUpdate] kafka-0-a7a43b22-9088-4b97-9672-8f8f82286b70 TASK_STARTING slave:#22-S3 reason:REASON_COMMAND_EXECUTOR_FAILED 2017-03-14 15:14:46,484 INFO KafkaMesosScheduler] [statusUpdate] kafka-0-a7a43b22-9088-4b97-9672-8f8f82286b70 TASK_FAILED slave:#22-S3 reason:REASON_COMMAND_EXECUTOR_FAILED...

gradle.build says scalaVersion = "2.11.8". Now, I'm not sure how do I verify I run it using same Scala. ``` Add mesos repo RUN \ apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv...

It turns out my gradle said Mesos version 0.28.0 while I'm running 1.1.0, so I'm testing that. kafka-mesos-0.10.1.0-SNAPSHOT-kafka_2.11-0.10.1.1.jar kafka_2.10-0.8.2.2.tgz Ahaaa. "build-image.sh" has hardcoded values! I missed that during the build....

it works. would you be interested in PR?