This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-15
Channels
- # aws (1)
- # beginners (6)
- # boot (25)
- # cider (30)
- # cljs-dev (50)
- # cljsrn (45)
- # clojure (98)
- # clojure-austin (5)
- # clojure-czech (1)
- # clojure-dev (21)
- # clojure-dusseldorf (29)
- # clojure-germany (2)
- # clojure-greece (117)
- # clojure-italy (2)
- # clojure-nl (4)
- # clojure-russia (26)
- # clojure-serbia (10)
- # clojure-spec (123)
- # clojure-turkiye (1)
- # clojure-uk (27)
- # clojured (13)
- # clojurescript (57)
- # core-async (18)
- # cursive (13)
- # datomic (20)
- # defnpodcast (16)
- # emacs (8)
- # events (2)
- # figwheel (3)
- # instaparse (1)
- # jobs (3)
- # jobs-discuss (39)
- # klipse (9)
- # lumo (100)
- # mount (1)
- # numerical-computing (1)
- # off-topic (22)
- # om (34)
- # onyx (17)
- # pedestal (1)
- # perun (29)
- # re-frame (60)
- # reagent (16)
- # remote-jobs (8)
- # rethinkdb (6)
- # ring-swagger (19)
- # rum (1)
- # slack-help (1)
- # specter (3)
- # untangled (1)
- # yada (17)
Anyone know if Onyx is supposed to balance peers across multiple jobs if you set the task scheduler to :onyx.task-scheduler/balanced
?
Let's say I submit a job and it gets all the peers assigned. Then I submit another job an hour later… Onyx will rebalance the peers to make sure my new job gets some of the available vpeers, right?
Oh, wait. Found it in the docs! > If a job is submitted while this scheduler is running, the entire cluster will be rebalanced. For example, if job A has all 100 peers executing its task, and job B is submitted, 50 peers will move from job A to job B.
Hey guys, I have an interesting question for you. I am going to try and explain this. We are attempting to use spandex ( an elasticsearch lib ) in a bulk task. What is interesting about this library is that the ES bulk task is built around using core.async channels. We are wondering how this might work inside of a bulk task or if it will?
Currently we are going to setup the channels in a lifecycle which get passed in to the bulk task using a param
You can use lifecycles to inject any state you may need, including core.async channels.
ok, I think its just feeling wierd to put stuff on a channel and then deal with the results on an ouput channel in a single task
Depending on what you need for reliability guarantees, it might be a better choice to use a plugin.