Hiya Vinod, thanks again for chiming in! Both frameworks are indeed binding to the same IP/interface, the kafka-mesos scheduler has LIBPROCESS_IP set, per its’ docs.
strace tells me that it tries to connect and then pretty much goes quiet. this socket does show as ESTABLISHED in netstat. — 0419 13:11:49.881398 30511 sched.cpp:222] Version: 0.27.1 I0419 13:11:49.890899 30556 sched.cpp:326] New master detected at [email protected]:5050 [pid 30556] connect(43, {sa_family=AF_INET, sin_port=htons(5050), sin_addr=inet_addr("10.100.1.158")}, 16) = -1 EINPROGRESS (Operation now in progress) I0419 13:11:49.892683 30556 sched.cpp:336] No credentials provided. Attempting to register without authentication [pid 30531] +++ exited with 0 +++ Process 30578 attached [pid 30552] +++ exited with 0 +++ -- From: Vinod Kone <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, April 19, 2016 at 1:08 PM To: user <[email protected]<mailto:[email protected]>> Subject: Re: kafka-mesos still refusing to launch brokers on one cluster On Tue, Apr 19, 2016 at 11:24 AM, Justin Ryan <[email protected]<mailto:[email protected]>> wrote: Marathon has no trouble registering a framework and launching jobs on this cluster, only kafka-mesos. :/ Are both these frameworks binding to the same IP/interface? Does anyone of them use any LIBPROCESS_IP or LIBPROCESS_PORT env variables? ________________________________ 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.
