This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-07
Channels
- # announcements (11)
- # architecture (2)
- # babashka (84)
- # beginners (226)
- # calva (7)
- # chlorine-clover (4)
- # cider (29)
- # clara (17)
- # clj-kondo (23)
- # cljs-dev (58)
- # cljsrn (60)
- # clojure (172)
- # clojure-europe (24)
- # clojure-finland (2)
- # clojure-italy (6)
- # clojure-nl (8)
- # clojure-spec (4)
- # clojure-uk (22)
- # clojurescript (44)
- # conjure (39)
- # core-async (64)
- # cursive (76)
- # data-science (15)
- # duct (3)
- # emacs (2)
- # events (5)
- # fulcro (30)
- # helix (4)
- # jackdaw (5)
- # juxt (1)
- # kaocha (1)
- # leiningen (4)
- # off-topic (9)
- # pathom (22)
- # re-frame (9)
- # reagent (33)
- # reitit (3)
- # ring (10)
- # ring-swagger (2)
- # shadow-cljs (192)
- # spacemacs (27)
- # specter (2)
- # sql (59)
- # vim (2)
hope it's okay to ask general kafka questions in here, sorry in advance if not 😬 does anyone know why my consumer lag often sticks at 1?
that's a little bit of the output from describing the consumer group, cmd.customer is a source and goes to 0, but customer is both a sink and a source, could that be the reason? I have basically two flows in the topology:
cmd.customer -> some internal topics -> customer
customer -> aggregation -> agg.customer
So cmd.customer has commands on
customer has events on
those get read to produce an aggregate on agg.customer@ULNRSUK8C are you using exactly-once semantics? If so, the kafka console tools will report the lag as 1 even when all messages have been processed
ahh, yes I am. Thanks, I guess just something I need to be aware of then, cheers!