This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (1)
- # aws-lambda (16)
- # beginners (8)
- # boot (2)
- # cider (4)
- # cljsrn (9)
- # clojure (137)
- # clojure-italy (3)
- # clojure-russia (39)
- # clojure-spec (34)
- # clojure-uk (33)
- # clojurescript (44)
- # core-logic (11)
- # cursive (27)
- # data-science (16)
- # datomic (52)
- # duct (1)
- # emacs (1)
- # figwheel (2)
- # fulcro (90)
- # graphql (3)
- # hoplon (7)
- # lambdaisland (2)
- # leiningen (23)
- # lumo (1)
- # off-topic (1)
- # om (40)
- # onyx (44)
- # re-frame (116)
- # reagent (3)
- # shadow-cljs (87)
is there a guide or an example how to update plugins from 0.9 to 0.11? 🙂 I want to update onyx-http, since we're using it and it's time to update Onyx finally, but
onyx-plugin template is oriented towards 0.9... I guess a suggestion of a simpler plugin would suffice, I can read the code, it's just onyx-kafka is pretty complex 🙂
@asolovyov it's best to look at existing plugins that have been upgraded and see what's changed
I'm looking at onyx-bookkeeper right now, since I've found comment in onyx-http that it was written after the former 🙂
G'day all. There doesn't seem to be a #pyroclast channel but I just thought I would drop a line to say that http://pyroclast.io/docs/guides/getting-started.html suggested
npm install -g pyroclast-cli is currently failing with
npm ERR! code 1 npm ERR! Command failed: /usr/local/bin/git checkout develop npm ERR! error: pathspec 'develop' did not match any file(s) known to git. npm ERR!
I have a question. Is it possible to use windows and triggers that output data to another task in the workflow?
how do peers coordinate between each other which tasks they run, and/or which job to start working on ? is that communicated through the log ?
trying to figure out whether i can observe from the log which jobs are currently being processed, and which ones are still in queue
Hey Guys, The battle continues with the Media Driver timeout. I separated out the media driver into a separate container in the same pod and got all of that working. One thing I noticed is in the onyx dashboard is shortly after submitting the job ( still idle no data to consume ) I start getting lots of events about peers leaving the cluster and joining ( :leave-cluster, prepare-join-cluster, :add-peer ). This goes on for a bit until eventually a time out occurs.
@camechis It sounds like the networking between your peer pods are having trouble communicating with each other on the ports they expose.
could the check point storage come into play at all with this issue ? Want to make sure our GCS implementation is not causing this
@camechis Unlikely unless you see stack traces in the onyx log's indicating that your storage impl is having issues.
Ok, good there. I switched to one physical peer and getting much better results. Think it's communication between the pods
Sounds right. If things appear okay and as soon as activity starts with a job you start seeing peers dropping off, it's likely that they tried to open connections to on another and the network channels do it aren't open.
Should have something like
- name: BIND_ADDR valueFrom: fieldRef: fieldPath: status.podIP
Also your media driver needs UDP open
ports: - containerPort: 40200 - containerPort: 40200 protocol: UDP