This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (2)
- # beginners (32)
- # boot (217)
- # cider (20)
- # cljsjs (25)
- # cljsrn (9)
- # clojure (87)
- # clojure-android (7)
- # clojure-austin (4)
- # clojure-belgium (10)
- # clojure-canada (13)
- # clojure-dev (28)
- # clojure-dusseldorf (2)
- # clojure-greece (119)
- # clojure-nl (1)
- # clojure-russia (22)
- # clojure-spain (3)
- # clojure-spec (81)
- # clojure-uk (54)
- # clojurescript (32)
- # community-development (2)
- # core-async (19)
- # cursive (18)
- # datascript (5)
- # datomic (1)
- # dirac (22)
- # emacs (22)
- # hoplon (198)
- # incanter (1)
- # instaparse (4)
- # jobs (3)
- # keechma (15)
- # ldnclj (2)
- # lein-figwheel (14)
- # mount (8)
- # om (78)
- # om-next (4)
- # onyx (37)
- # other-languages (1)
- # pedestal (6)
- # re-frame (22)
- # reagent (25)
- # ring-swagger (17)
- # robots (1)
- # slack-help (1)
- # spacemacs (7)
- # specter (50)
- # spirituality-ethics (3)
- # uncomplicate (5)
- # untangled (1)
- # yada (17)
Choco is really neat. I played with it awhile back to pick fantasy basketball teams for a friend (using constrained knapsack): https://gist.github.com/hadronzoo/7916c32c0d434c9e7dc5#file-core-clj
Probabilistic models are much better for the fantasy basketball problem, but it was still fun.
@lanejo01: > any tips on getting started in distributed systems Maybe start with the CAP theorem and its critique by Martin Kleppmann. I was super lucky to have my first distributed systems talk be by Kleppmann talking about the CAP theory at Strangeloop 2015.
Watching it right now 🙂 Thanks @drewverlee !
We're putting together a self-help guide that has a series of questions that you can answer to diagnose common problems with your Onyx program. Does anyone have thoughts on whether this would be best as a static page with links to jump around between, or something more visual like a flow chart?
Been leaning in that direction. I imagine anyone using it will eventually want to read everything in its entirety and not need to click around to navigate.
Oh, I should mention that the reason a flow chart might be interesting is that some of the questions to determine what the problem is are several deep. e.g. "Is X true?", yes -> "Is Y true?"
Sounds possibly interesting but hard to reason about unless I considered some of the actual flows. I wonder if you could encode some of that in a doc.
I think in a doc it would look like:
What's the state of X? - [It is A](link-1) - [It is B](link-2) ...
Where link 1/2 are anchors into the same doc
Looking at the onyx dashboard (very cool!) - one of my jobs shows blank under "Host Allocation". Does that mean there are no peers available to do the work?
@devn: I think so. Can I see a screenshot?
It says its running, so perhaps its a bug in the dash. o-o
I went back and re-submitted with
NPEERS=3 and the job ran, but the old one continues to spin
You should kill off your old one.
(don't fully understand what the significance of NPEERS is, and why more than enough would casue it to not run)
It wouldn't ^
Check out the scheduler chapter of the user guide to learn about that, btw.
onyx.api/kill-job on the job ID
I thought we left kill-job in the dashboard, and just ditched restart-job. It’d be good to add kill-job back in at least. Anyway, yes onyx.api/kill-job
Can I do that from a local repl if I point it at the prod zookeeper? Or what's the normal workflow for submitting/restarting/killing jobs?
Yes to the first question. Latter part depends on your set up, we've done it a few different ways. Depends on the customer
This might be helpful, too. See the Clojure part and HTTP server below: https://github.com/onyx-platform/lib-onyx#replica-queries
Just another way to see what's going on.
It would be nice to have a cohesive command line tool to do submission/restarts/job killing. I think that needs to come out of the community organically though.
Got it. I'm assuming a CLI would hit the endpoints provided by
(require '[lib-onyx.lib-onyx.replica-query-server :as rqs]) (def server-port 3000) (def server (rqs/start-replica-query-server peer-config server-port)
Yep yep 🙂
@devth: I’m working on a kubernetes example for onyx-twitter-sample and just remembered how to handle the shm issue,
will create a volume as a section of the hosts memory
- name: aeronshm emptyDir: medium: “Memory”