This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (63)
- # beginners (1)
- # boot (83)
- # cider (17)
- # clojure (33)
- # clojure-android (3)
- # clojure-france (3)
- # clojure-gamedev (1)
- # clojure-russia (20)
- # clojure-sg (9)
- # clojurescript (81)
- # core-async (77)
- # cursive (13)
- # datomic (30)
- # hoplon (7)
- # instaparse (54)
- # ldnclj (1)
- # off-topic (4)
- # om (2)
- # onyx (23)
- # re-frame (16)
- # reagent (3)
- # yada (2)
If you want the properties of kafka without managing it, you could use amazon kinesis
what's the effect of
:onyx/batch-size in a catalog entry when you don't have
:onyx/bulk set to true? I am suspicious that my setup stops working after the batch-size is hit, and I'm probably misconfiguring something here...
:onyx/batch-size to Long/MAX_VALUE eliminates the symptom, but I think it might not be fixing the actual problem here
@noisesmith: Batch size is a performance knob that scoops up messages together before performing actions. It's to increase the payload being sent over the wire in the case that a single message leaves you network bound.
:onyx/bulk? is simply a functional application to all the segments collected by the batch. Bulk and batch-size have no functional correctness properties that tie them together.
for some reason my workflow just stopped accepting tasks after a certain number were handled, and upping batch-size eliminated the symptom
Are there exceptions in onyx.log? It sounds like your batch was partial processed and blew up.
no errors, but I do see the suspicious looking message "Lifecycle chose not to start the task yet. Backing off a nd retrying..."
FYI, we're going to be putting on private training sessions about creating, managing, and monitoring Onyx infrastructure if your place is interested.
Email <mailto:[email protected]|[email protected]> if/when you want to try it. Still crafting the material for it, but we'd like to do one-on-one sessions with companies and tailor the content to their problem domain.
@michaeldrogalis: thanks for the tip about onyx.log - I had a separate issue in my job code and hadn't been watching that log file for stack traces. Is it possible to turn off ansi coloring in that file? I assume this is being done by some stack trace prettifier that onyx is pulling in