mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinit Mahedia <>
Subject Re: mesos/kafka issues (reviving old thread)
Date Fri, 03 Jun 2016 21:19:05 GMT
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).


Is there any alternative for getting kafka up and running on mesos  other
than this - mesos/kafka <> ?

On Fri, Jun 3, 2016 at 3:53 PM, Justin Ryan <> wrote:

> Hiya Vinit,
> I’ve made some progress, I have a conditionally working setup, and another
> setup which was working now failing in new ways.
> It does sound like your captures are similar to mine, what I found is that
> if I run the scheduler on, say, zk01 (which is also a mesos-master), while
> it is the leader, things work fine.  If mesos-master fails over to zk02 or
> zk03, the scheduler running on zk01 stops working, though its’ config
> points at all three machines.  Obviously this makes it difficult to run the
> scheduler itself as a mesos task.
> Though I wish neither of us were having this problem, it’s good to not
> feel like I’m crazy, I kinda ran out of things to test until one day it
> occurred to me to check if it matters whether the scheduler runs on the
> active mesos-master.  I can think of a couple reasons this would be so, but
> haven’t had time to narrow it down.
> Cheers!
> Justin
> On 6/3/16, 12:52 PM, "Vinit Mahedia" <> wrote:
> >
> >
> >​​Hey Justin,
> >
> >
> >I am running in the same issues as you mentioned in this old
> > thread <
> did you resolve it?
> >
> >
> >I see that kafka framework sends a POST request to register itself but
> mesos master logs does not even show that the request was received, packet
> capture does. My guess was that something is
> > wrong in HTTP request but doing this same thing on local setup works
> fine so that can't be the case. I can capture the requests on the master
> node so there's no network issues either, just like in your case. I also
> verified that two machines can communicate
> > on using netcat as well.
> >
> >
> >
> >Like you mentioned in your thread, once it registered with mesos but that
> was the only time that happened, the brokers did not start even then -
> "start" timed out.
> >
> >
> >^that behavior hints at possible bug in mesos, where it sits on this
> request for too long and some times under some conditions, it gets through,
> that's when it works.
> >
> >
> >PS I have network capture showing POST from framework to master, if
> anyone wants to take a look at it.
> >
> >
> >--
> >Vinit
> >
> >
> ________________________________
> 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.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message