@dave.dixon i think Onyx upgraded ZK (specifically, curator
)to a more recent version in 0.13, but there were some issues with curator-test
which was left on the old version
i'm using the latest version of curator/ZK myself (because I need a recent guava
) and haven't experienced any issues so far
@lmergen Thanks. Do you know what version of ZK server you're running?
3.3.6
Interesting. I'll poke around in the deps analysis and see if something else might be interfering. I'll also give 3.3.6 a try if I can.
Onyx won't start at all with ZK 3.3.6, just hangs when trying to connect.
The version of Kafka I'm running also seemed to have trouble with 3.3.6.
@lmergen did you mean 3.3.6? That’s really old, but you say you’re using the latest version of ZK?
hmmm I’m using the latest tag on docker
oops, i read it wrong indeed
3.4.12 it is
I wonder if the issue is something to do with curator test and resolution with tools-dep then
Maybe we need some instructions to switch everything over together with exclusions, or just force users to provide both. Dependencies with zk and kafka can be tough with all of the versions floating out there in prod deployments
don’t forget about us poor google cloud users :)
i still need to override guava
i’ve documented it here though => https://github.com/solatis/onyx-google-pubsub
Right yep
How’s it working out for you?
good! running stable since release, 3 node cluster
Great :)
At some point we can bring it into the official onyx org, and give you commit access. That is, assuming you’re interested.
yes would be good, i would like to make a few more changes in usability before that
there are some things regarding authentication i would like to improve
Great. Yeah, better to wait until you’ve iterated on it enough :)
@lmergen Are you using onyx-kafka, or the kafka-clients lib?
not using kafka
@lucasbradstreet exactly, i’ll give you a nudge when i think it’s fully stable.
@lucasbradstreet Not sure if it's relevant, but here are the logs ZK gives when the exception occurs.
Got it working after excluding ZK enough places and referring 3.4.12.
Great. That was what I was about to suggest once I saw “unknown type 15” in the logs and did some googling
It’d be helpful to know which libs you needed to exclude it from - especially anything we can improve on our side.
on that note, @lucasbradstreet -- would it be possible to move curator-test to the :test profile? or is this related to the onyx-test-env ?
Yeah, I think that’s a good idea. I’ve been hesitant about breaking user code but I think it probably has to be done
I have some backlog work to do with migrating all our projects to circleci 2, but if you want to send us a PR after doing a little testing I’d appreciate it
sure
I'll try and figure out the minimal exclusions.
Here's what I wound up with.