Can kubernetes and mesos+marathon work together in some way? In the docs you recommend both so I wonder if I'm missing something.

hey, i know this is actually off-topic for this channel, but since there’s a big overlap, i’m asking the question in here anyway if that’s okay

(i have a question about kafka)

so, i downloaded the onyx-commander-example and everything seems to be working fine — tests pass, so my setup works

i saw that the project was using gregor, so i decided to try that out myself… but i’m getting completely weird errors with this code:

(ns kafka-test
  (:require [gregor.core :as g]))


(def kafka-zookeeper "127.0.0.1:2181")
(println "topics = " (pr-str (g/topics {:connection-string kafka-zookeeper})))
(g/create-topic {:connection-string kafka-zookeeper} "foobar-wombat" {})

@yonatanel Kubernetes can run on Mesos, however last time I checked the Kubernetes-Mesos version was pretty far behind upstream Kubernetes. Onyx can run on both platforms.

@lmergen hmm what kind of errors?

baiscally, the create-topic is breaking over some SINGLETON field not being recognized: https://glot.io/snippets/eoqy6ebx6d

it’s important to note that the (g/topics) command is properly listing the topics

so communication seems to work

but… i’m puzzled by this error, and wasting several hours on it now

Can you provide a gist of the error?

yeah i’ll post everything on GH, one moment!

https://gist.github.com/solatis/b227b1199f1ecaf5c5639db5cc854c98

mondrian.cqrs..... is my namespace

Make sure your Kafka client and server versions match, I've seen some pretty ambiguous errors when they don't match.

aha, right!

i’ll try flushing my dependencies cache

Looks like the latest Gregor is running 0.10.0.1

https://github.com/onyx-platform/onyx-commander-example/blob/master/project.clj#L15

and there you’re using 0.10.1.1 🙂

perhaps my library include order is not the same, causing some different versions to be chosen… hmz

Sorry mobile right now, the above was a typo heh. Gregor is on [org.apache.kafka/kafka_2.11 "0.10.1.1"]

ok 🙂

perhaps i should just be using franzy, since that seems to be working for onyx-kafka…

Are you using the docker compose from the Onyx-commander repo?

yep

let’s see what that does

Yea hmm, it's very odd that the tests pass in Onyx-commander but not for you locally.

yeah, i’m 80% sure it’s an environment thingie

dare i say, 90% sure

what the fudge… franzy is giving the exact same error

I can try and reproduce this error if you can publish a minimal failing case.

ERROR in (end-to-end-test) (MarkerFactory.java:52)
Uncaught exception, not in assertion.
expected: nil
  actual: java.lang.NoSuchFieldError: SINGLETON
 at org.slf4j.MarkerFactory.<clinit> (MarkerFactory.java:52)
    org.apache.log4j.Category.<clinit> (Category.java:53)
    org.I0Itec.zkclient.ZkConnection.<clinit> (ZkConnection.java:40)
    franzy.admin.zookeeper.client$make_zk_connection.invokeStatic (client.clj:11)
    franzy.admin.zookeeper.client$make_zk_connection.invoke (client.clj:8)
    franzy.admin.zookeeper.client$make_zk_utils.invokeStatic (client.clj:29)
    franzy.admin.zookeeper.client$make_zk_utils.invoke (client.clj:25)

is it a logging issue ? can it be ?

…. mother of god…. it IS a logging issue 😕

that was literally the only difference, i included timbre in my deps

i removed that include, and… tada, it worked

what the hell 😕

@gardnervickers thanks for your support! 😉

Huh that's incredibly strange. Welp glad to hear you're sorted now

fwiw, i always include these libraries in my projects when using timbre:

[com.taoensso/timbre "4.8.0"]
   [com.fzakaria/slf4j-timbre "0.3.2"]
   [org.slf4j/log4j-over-slf4j "1.7.21"]
   [org.slf4j/jul-to-slf4j "1.7.21"]
   [org.slf4j/jcl-over-slf4j "1.7.21"]

removing all those includes fixed this issue

sigh

sorry for the noise 😉

@lmergen Only here for a sec, then I gotta run. Only reason I used Gregor here was to make it easier for the direct audience of that example. 99% of the time I use the Kafka bindings directly now to avoid indirect version mismatches. Which, as you’ve found, is super annoying.

thanks michael, that is a useful tip. i might start doing that as well

@lmergen my guess is it was an issue with SLF4j versioning.

yes, it’s probably something like that. well, another afternoon ruined, another lesson learned 🙂

@lmergen https://www.slf4j.org/faq.html#IllegalAccessError

that’s it

that’s exactly the error i was seeing indeed

This can likely be resolved with the right :exclusions