This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-02
Channels
- # aleph (5)
- # beginners (112)
- # boot (137)
- # cider (10)
- # cljs-dev (36)
- # cljsrn (2)
- # clojure (118)
- # clojure-argentina (1)
- # clojure-berlin (1)
- # clojure-brasil (3)
- # clojure-dev (4)
- # clojure-italy (2)
- # clojure-nl (13)
- # clojure-russia (23)
- # clojure-spec (5)
- # clojure-uk (53)
- # clojurescript (344)
- # clojutre (1)
- # core-async (65)
- # cursive (9)
- # datascript (7)
- # datomic (28)
- # devops (1)
- # emacs (16)
- # events (1)
- # jobs (5)
- # keechma (18)
- # lumo (56)
- # off-topic (7)
- # om (3)
- # onyx (14)
- # protorepl (21)
- # re-frame (3)
- # reagent (20)
- # ring (12)
- # ring-swagger (9)
- # specter (17)
- # unrepl (14)
- # vim (14)
- # yada (22)
@lmergen do you have the kafka lifecycles as part of your job? e.g.
{:lifecycle/task :read-messages
:lifecycle/calls :onyx.plugin.kafka/read-messages-calls}
@lucasbradstreet no i dont have any lifecycles at all
that’d be it
you need the lifecycles described in the README, yep.
otherwise it won’t call handle-exception to decide whether to restart or kill the job, and will just default to kill
default kill is the default error handling
no worries
in the past the plugin wouldn’t have worked at all, but more of the logic is in the plugin start/stop now
no worries. Glad it’s not a bug in onyx. I remembered that we had a bug in our custom handle-exception lifecycle previously, which is why we saw the same thing.