This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-17
Channels
- # bangalore-clj (1)
- # beginners (23)
- # boot (141)
- # cider (68)
- # cljs-dev (29)
- # cljsjs (1)
- # cljsrn (11)
- # clojure (150)
- # clojure-austin (3)
- # clojure-berlin (1)
- # clojure-france (2)
- # clojure-greece (13)
- # clojure-italy (5)
- # clojure-russia (49)
- # clojure-spec (15)
- # clojure-uk (45)
- # clojurescript (152)
- # code-art (1)
- # core-async (75)
- # cursive (12)
- # datascript (2)
- # datomic (90)
- # dirac (5)
- # emacs (10)
- # garden (1)
- # hoplon (52)
- # instaparse (4)
- # juxt (2)
- # lein-figwheel (2)
- # lumo (47)
- # mount (94)
- # off-topic (20)
- # om (21)
- # onyx (14)
- # parinfer (19)
- # pedestal (3)
- # protorepl (13)
- # re-frame (5)
- # reagent (20)
- # slack-help (10)
- # spacemacs (8)
- # specter (57)
- # unrepl (11)
- # untangled (3)
- # vim (1)
- # yada (1)
I wonder if it's possible somehow to delay execution of a job? Like, do something on an arrival of Kafka message, but after a minute.
best thing you could do is buffer it into a window and then have a trigger on a timer that does something
Hey all, what’s the maximum value :onyx/pending-timeout
can take? I’m getting “Pending timeout cannot be greater than acking daemon timeout” error, but can’t find what’s the value of acking daemon timeout is
@jetmind Yep, with 0.9 that value can be as large as you want it, so long as the acking daemon value stays above it.
Those two values are interdependent for message replay, which is why Onyx throws that message back.
@jetmind It’s the amount of time that a message’s lineage is flushed from memory, presumably because the message was lost in transit and needs to be replayed. The higher the value, the less frequently clean up will take place.
Higher value = more memory consumption, less thread activity. Lower = the inverse.
Anytime!
Anyone planning on being at Clojure/west later in the month?