This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-03
Channels
- # aleph (1)
- # beginners (42)
- # boot (34)
- # cider (157)
- # cljs-dev (12)
- # cljsrn (3)
- # clojure (165)
- # clojure-conj (1)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-russia (20)
- # clojure-spec (27)
- # clojure-uk (173)
- # clojurescript (116)
- # cursive (30)
- # datomic (87)
- # devcards (1)
- # docs (9)
- # emacs (2)
- # ethereum (2)
- # events (2)
- # fulcro (60)
- # graphql (10)
- # hoplon (2)
- # jobs-rus (6)
- # keechma (1)
- # lein-figwheel (9)
- # leiningen (36)
- # luminus (2)
- # mount (3)
- # off-topic (16)
- # om (14)
- # onyx (12)
- # pedestal (19)
- # portkey (107)
- # re-frame (9)
- # reagent (5)
- # ring (26)
- # shadow-cljs (149)
- # spacemacs (3)
- # sql (6)
That was a great talk. Good stuff @georgek ^^
Thanks! It was a lot of fun and some great questions! @maxk ours was a single instance approach. For our very conservative org, being able to deploy as a simple uberjar with not new system dependencies was a huge selling point!
@lucasbradstreet 25 for 8-core server/32gb ram. 25 is because there was 24 catalog functions, we've reduced it to 5 now
@georgek our motivation using ONYX to have horizontal scalability for free (well, almost for free). This is the third version of our stream processing/semantic reconciliation framework, two prev was implemented using python.
hi all, i'm having some trouble starting onyx with an out of process aeron media driver. my env and peer properties: :env-config {:zookeeper/server? false, :onyx.log/config {:level :info}, :onyx/tenancy-id hello1, :zookeeper/address 127.0.0.1:2181, :zookeeper.server/port 2181}, :peer-config {:onyx/tenancy-id hello1, :onyx.messaging/allow-short-circuit? true, :onyx.messaging/impl :aeron, :onyx.log/config {:level :info}, :onyx.messaging/peer-port 40200, :zookeeper/address 127.0.0.1:2181, :onyx.peer/job-scheduler :onyx.job-scheduler/balanced, :onyx.messaging.aeron/embedded-driver? false, :onyx.peer/zookeeper-timeout 60000, :onyx.messaging/bind-addr localhost} Running the aeron media driver as a separate process: (let [ctx (doto (MediaDriver$Context.)) media-driver (MediaDriver/launch ctx)] (println "Launched the Media Driver. Blocking forever...") (<!! (chan))) But I don't see any of the virtual peers started in the logs (and nothing in the onyx dashboard). Changing to an embedded driver allows the peers to start
@ben.mumford any errors on the media driver side? I would think that would be enough.
@lellis we build the media driver included in onyx core into a containers https://github.com/onyx-platform/onyx/blob/0c75732de8d9228c5a9450484abb939ea8d4d480/src/onyx/messaging/aeron_media_driver.clj