This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-13
Channels
- # admin-announcements (1)
- # beginners (10)
- # boot (15)
- # cider (9)
- # clara (195)
- # cljsrn (24)
- # clojars (20)
- # clojure (46)
- # clojure-android (1)
- # clojure-germany (15)
- # clojure-greece (16)
- # clojure-nl (1)
- # clojure-russia (13)
- # clojure-spec (28)
- # clojure-uk (44)
- # clojurescript (104)
- # clojurex (1)
- # component (7)
- # css (2)
- # cursive (27)
- # datomic (92)
- # dirac (12)
- # emacs (5)
- # lambdaisland (3)
- # lein-figwheel (36)
- # mount (87)
- # off-topic (8)
- # om (102)
- # om-next (3)
- # onyx (30)
- # pedestal (3)
- # re-frame (26)
- # reagent (20)
- # robots (4)
- # specter (18)
- # spirituality-ethics (1)
- # untangled (127)
- # yada (11)
@michaeldrogalis: How's franzy progress? 🙂
@acron: we have a Kafka plugin update ready to merge but we're blocked on how to handle compatibility with both 0.8 and 0.9
@lucasbradstreet: that was my next question 🙂
@acron: Any suggestions?
We have a Kafka 0.8 and 0.9 plugin, both working, both with totally different impls and dependencies, both with the same interface.
Yeah it's a hard one, heh.
I dont think so, too many people still use 0.8
You can still use the snapshot version of 0.9 though, thats on Clojars already.
I'd like to be able to do :kafka/version
:0.8
/ :0.9
in the catalog entry, but I can't see a way to not have a cage-match between the dependencies at runtime..
Are there any gotchas on segment retries? I have a test which is looping, but I can't understand if I caused it. We're pretty baffled. It's possible we caused it somewhere, but is there some failure that I might be tripping?
@bfaber: The default time that a segment must complete within before it is retried is 60 seconds. What's the mean latency for your segments to run through the workflow?
@bfaber: http://www.onyxplatform.org/docs/cheat-sheet/latest/#catalog-entry/:onyx/pending-timeout
@michaeldrogalis: A thousand thanks! That did it, I am now happily not looping. 🙂
@bfaber: Cool, glad to hear it.
@joe.lane: Onyx uses BtrPlace to schedule virtual peers on tasks. BtrPlace uses Choco Solver.
Awesome, I have no idea what that is! Unfortunately i’m new to distributed systems so I don’t know what scheduling virtual peers on tasks means, however I know what choco is does so BtrPlace must be doing some cool stuff. Thanks for the quick response, any tips on getting started in distributed systems other than just go through onyx?
@joe.lane: Read lots of papers 🙂 If you make your way through Onyx, there's a chapter in the User Guide dedicated to explaining how scheduling works.
@joe.lane: It's a pretty broad field, depends on what you want to learn. Maybe something by Lamport, he started a lot of the fundamentals. http://amturing.acm.org/p558-lamport.pdf
Someone else might have a good suggestion though.
It's hard to jump right in without any keywords to know to look for, I found Kyle Kingsbury's posts and talks on distributed databases really great as a stepping off point