This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-13
Channels
- # beginners (71)
- # boot (61)
- # clara (49)
- # cljs-dev (9)
- # cljsjs (2)
- # cljsrn (5)
- # clojure (55)
- # clojure-android (1)
- # clojure-italy (4)
- # clojure-spec (39)
- # clojure-uk (56)
- # clojurescript (69)
- # cursive (5)
- # data-science (1)
- # defnpodcast (6)
- # devcards (1)
- # duct (12)
- # figwheel (3)
- # fulcro (18)
- # leiningen (35)
- # lumo (19)
- # midje (1)
- # off-topic (22)
- # om (3)
- # onyx (23)
- # portkey (3)
- # re-frame (20)
- # reagent (23)
- # ring-swagger (6)
- # shadow-cljs (119)
- # specter (7)
- # unrepl (25)
@lmergen I’m heading off to bed, but if you PM me some info about the cluster setup (number of nodes, jobs, tasks, and their max peer parameters), that’d help. Also try out 0.12-alpha4 if you haven’t already.
Sure thing :)
Also, an onyx.log somewhere with private info stripped out would help
@lucasbradstreet thank you for the sunday night help. I'll look into the windowing
@camechis if you’re still having your media driver problem, I️ don’t think Kubernetes properly evicts old conntrack entries for services using UDP. One workaround would be to add a new endpoint to your service after booting your peers, forcing Kubernetes to clear the old conntrack entries. I️ ask about the readinessCheck because we have one on our media driver, which prevents a new endpoint from being added to a service until after passing a media driver readiness check.
@gardnervickers We finally managed to get it running by changing the term-buffer-size.segment as suggested by Lucas. That is good to know though
I am attempting a high throughput job but I keep running into memory and zookeeper issues
I think since we were having so many problems lucas gave that to me as a very small one to see if it works
so far so good with it. One thing effecting us is we are on a 5 node k8 cluster ( 4 cores, 16 gigs each ) that is pretty packed right now
Thats the only thing I can think of because we weren’t doing much at the time. With the default settings in 0.11 our job would not even launch. Also tried the settings on 0.12 which is somewhere in the middle
Ah great, thanks!