Justin, There's certainly a bug somewhere, either in mesos kafka framework or mesos itself. If I can get this mesos master running under debugger, this would be over in maybe few hours or few days.
Kafka is a stateful service so can't run on marathon directly, there has to be some framework/wrapper which manages brokers - Read here <https://mesosphere.com/blog/2015/07/16/making-apache-kafka-elastic-with-apache-mesos/> . On Fri, Jun 3, 2016 at 4:36 PM, Justin Ryan <[email protected]> wrote: > inline > > On 6/3/16, 2:19 PM, "Vinit Mahedia" <[email protected]> wrote: > > >Justin, > >Yeah - as long as everything is on a single box (mesos-kafka scheduler, > mesos-master, zk etc.) > >things work just fine, which is what I meant by local setup. > > > > > >I did a local cluster setup as well, 3 vagrant machines, where it does > >not work. So it does not work at all > >if you have multi node setup (vagrant machines or bare metal). > > > > I do have two working clusters, but the mesos-kafka scheduler must run on > the active mesos-master leader, which may also be an indication of another > symptom that just *happens* to coincide with this. > > > > >others, > > > >Is there any alternative for getting kafka up and running on mesos other > than this - > >mesos/kafka <https://github.com/mesos/kafka> ? > > > > I thought about this for a while, but digging into the code, this is just > an extension of MesosFramework, which is core mesos functionality. > > We’re either missing something or have exposed a bug. > > Of course, a person could just run kafka brokers with marathon, but I > think this is worth the trouble and is fundamentally how things should be > done. > > > ________________________________ > > P Please consider the environment before printing this e-mail > > The information in this electronic mail message is the sender's > confidential business and may be legally privileged. It is intended solely > for the addressee(s). Access to this internet electronic mail message by > anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be > taken in reliance on it is prohibited and may be unlawful. The sender > believes that this E-mail and any attachments were free of any virus, worm, > Trojan horse, and/or malicious code when sent. This message and its > attachments could have been infected during transmission. By reading the > message and opening any attachments, the recipient accepts full > responsibility for taking protective and remedial action about viruses and > other defects. The sender's employer is not liable for any loss or damage > arising in any way. > -- ~Vinit
