This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-21
Channels
- # aws (2)
- # bangalore-clj (14)
- # beginners (20)
- # boot (20)
- # cider (7)
- # cljs-dev (38)
- # cljsrn (13)
- # clojure (487)
- # clojure-argentina (3)
- # clojure-dev (15)
- # clojure-gamedev (4)
- # clojure-italy (3)
- # clojure-poland (1)
- # clojure-russia (1)
- # clojure-spec (25)
- # clojure-uk (47)
- # clojurescript (127)
- # datomic (125)
- # defnpodcast (1)
- # hoplon (27)
- # jobs (4)
- # lein-figwheel (2)
- # leiningen (1)
- # luminus (5)
- # off-topic (3)
- # om (25)
- # onyx (9)
- # parinfer (3)
- # pedestal (20)
- # planck (65)
- # re-frame (43)
- # reagent (4)
- # remote-jobs (1)
- # ring-swagger (2)
- # rum (9)
- # spacemacs (1)
- # unrepl (37)
- # vim (1)
guys, can I have two set of workers separated data center ? I want to run specific kinds of jobs an one them
@lxsameer It’s not recommended to run a single onyx cluster over multiple data centers. Latency will be hard to adjust around, and will create problems. A better approach would be to run one Onyx cluster in each data center.
@gardnervickers latency wouldn't be problem for my use case, I have several long running jobs which I want to setup some else and store the output in a data store
I’m talking more about latency between Zookeeper and Onyx, not so much latency within your job.
It’ll require tweaking various timeouts quite a bit. Is there any reason why multiple Onyx clusters won’t work for you use case?
It could work, but I’d recommend solving whatever problem you’re up against with a different approach rather than doing cross datacenter Onyx.