Justin, When you say "working" - does it mean kafka-scheduler still has to be on the same box as mesos-master? or you have it working without that constraint?
On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan <[email protected]> wrote: > inline > > On 6/8/16, 4:06 PM, "Justin Ryan" <[email protected]> wrote: > > >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this problem went > away. FWIW, I’m actually using a branch which updates kafka to 0.10.0.0 as > well: > > > > Correction: 0.9.5.1 (current git master) > > > PR for kafka 0.10.0.0 (tests still fail, someone else did the bulk of > porting but didn’t PR it) : https://github.com/mesos/kafka/pull/220 > > ( ./gradlew jar –x test gets a successful build ) > > > > Issue for the problem discussed in this thread: > https://github.com/mesos/kafka/issues/199 > > > >Cheers! > > > > > ________________________________ > > 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
