This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-01
Channels
- # beginners (133)
- # boot (59)
- # cider (5)
- # cljs-dev (30)
- # cljsrn (23)
- # clojure (212)
- # clojure-austin (3)
- # clojure-brasil (1)
- # clojure-chicago (5)
- # clojure-italy (10)
- # clojure-russia (5)
- # clojure-serbia (1)
- # clojure-spec (34)
- # clojure-turkiye (2)
- # clojure-uk (132)
- # clojurescript (163)
- # clojutre (1)
- # cursive (5)
- # datomic (58)
- # emacs (42)
- # events (1)
- # graphql (26)
- # hoplon (16)
- # jobs (1)
- # lumo (27)
- # numerical-computing (3)
- # off-topic (127)
- # om (9)
- # onyx (24)
- # re-frame (20)
- # reagent (20)
- # ring-swagger (14)
- # sql (19)
- # unrepl (28)
- # untangled (3)
- # vim (8)
- # yada (17)
i’m trying to understand what exactly is going on here. after running an ETL task for a long time, I’m getting a kafka exception that it “could not locate any kafka brokers to connect to” — with recoverable?
set to true
after that, it appears as if onyx is restarting the task, but it never fully recovers
recoverable is checked in the handle-exception lifecycle here https://github.com/onyx-platform/onyx-kafka/blob/0.10.x/src/onyx/plugin/kafka.clj#L336
which will allow the peer to restart and try to continue the job
Ah, it looks like it’s happening during initialization, which is not something we allow it to be restarted from. I thought we had resolved that issue though.
That’s a bug for sure
I’m logged an issue here https://github.com/onyx-platform/onyx/issues/789. I thought this was resolved, but I am going to have to track down whether it was fixed or not.
this is something that has affected us previously, so I will try to track it down asap.
Yeah we definitely hit and fixed this in the last 8 weeks. We’ll get it figured out ASAP, sorry about this one.
no problem, this is not in production yet — it’s a poor dev server that’s under immense load all the time
@lmergen Ahh, okay. Thanks for the report anyway, it’s high priority for us regardless 🙂