Joe Stein

you need libmesos so that the scheduler can talk (The Driver) to the master and master to scheduler, there are java bindings that you can build to https://github.com/groupon/jesos if you...

You have to set `kafka.metrics.reporters=ly.stealth.kafka.metrics.KafkaBrokerReporter` in file:server.properties or --options (depending on how you are launching the scheduler) so Kafka can start that reporter when the broker starts

@sherzberg we found a bug that is in the latest release https://github.com/mesos/kafka/releases/tag/v0.9.1.4 you should try to see if that resolved your problem

Setting the bind for the broker (which is what is advertised from Kafka) is an existing feature on broker add/update commands. ``` --bind-address broker bind address (broker0, 192.168.50.*, if:eth1). Default...

Hey @d4goxn any chance to reproduce in a vm setup? You don't need anything else except for what you are doing but you shouldn't be getting test failure. No mesos...

We have been talking about adding to the scheduler interface the bootstrap response for beta data. This way the scheduler should "talk" like a broker and be able to then...

seems like you maybe already set the user to vagrant launched the framework and then changed the user after... i believe mesos has an issue with that you might have...

Hey @JohnOmernik it sounds like good resolution would be an update to the scheduler. The scheduler could accept the connection for the meta data request and facilitate it. The scheduler...

ergh, sorry will get that fixed in another day or so, have some more testing on PR for another release too will fix the prior first thanks

Hey @mindscratch we modified kafka-manager for some of these https://github.com/stealthly/kafka-manager but not sure how maintainable that is going to be with upstream/downstream re-base. It would be great to have a...