This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-17
Channels
- # admin-announcements (104)
- # adventofcode (3)
- # aws (1)
- # boot (651)
- # cljs-dev (21)
- # cljsrn (12)
- # clojure (81)
- # clojure-china (1)
- # clojure-germany (1)
- # clojure-miami (2)
- # clojure-nl (8)
- # clojure-russia (19)
- # clojurescript (208)
- # core-typed (1)
- # cursive (19)
- # datavis (55)
- # datomic (57)
- # events (1)
- # hoplon (102)
- # ldnclj (12)
- # leiningen (8)
- # off-topic (11)
- # om (127)
- # onyx (21)
- # parinfer (2)
- # portland-or (3)
- # proton (2)
- # re-frame (2)
- # reagent (6)
@yusup ah yes, I've seen that before. It's probably caused by an underlying issue like a long GC pause causing a timeout in Aeron. I suggest you switch on the G1GC in Java and increase the Aeron client liveness timeout
See client liveness in https://github.com/real-logic/Aeron/wiki/Configuration-Options
You may also want to try switching on flight recorder and have a look at your GC events
Can you paste the stack trace. We’ll provide a better error
Either way is fine
@lucasbradstreet: "New monitoring metrics: zookeeper-write-exception and zookeeper-write-exception” https://github.com/onyx-platform/onyx/blob/0.8.x/changes.md
I like that we write the exception that kills the job to ZK. But that won't be useful for you
@robert-stuttaford: ah @bcambel told me how I didn't read it right :p