This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-16
Channels
- # admin-announcements (14)
- # announcements (1)
- # aws (1)
- # beginners (105)
- # boot (609)
- # braid-chat (4)
- # braveandtrue (3)
- # cider (24)
- # cljs-dev (13)
- # cljsrn (2)
- # clojure (142)
- # clojure-berlin (7)
- # clojure-ireland (7)
- # clojure-japan (10)
- # clojure-nl (4)
- # clojure-poland (76)
- # clojure-russia (198)
- # clojure-sg (4)
- # clojure-taiwan (1)
- # clojurebridge (1)
- # clojured (4)
- # clojurescript (73)
- # conf-proposals (11)
- # cursive (10)
- # datomic (32)
- # devcards (1)
- # dirac (22)
- # editors (5)
- # emacs (3)
- # events (4)
- # funcool (19)
- # hoplon (18)
- # job (1)
- # jobs (3)
- # jobs-rus (16)
- # keechma (25)
- # ldnclj (33)
- # lein-figwheel (10)
- # leiningen (4)
- # luminus (1)
- # off-topic (19)
- # om (255)
- # onyx (51)
- # overtone (1)
- # parinfer (206)
- # perun (5)
- # proton (2)
- # re-frame (3)
- # reagent (2)
- # remote-jobs (13)
- # ring-swagger (7)
- # slack-help (4)
- # yada (7)
are checkpoints scoped to onyx/ids?
that is, if i switch onyx/id, i’m also effectively switching checkpoints?
@robert-stuttaford: by default they are scoped to the job, however checkpoint/key allows them to be scoped to whatever you want
ok. so if i specify a checkpoint/key, even if i change onyx/id, it’ll continue to use that checkpoint information?
Yes I'm pretty sure
The point is to to give you a way to transition between deployments
ok. this helps me to understand why i’m struggling. i had this idea that checkpoints were scoped to onyx/id
to be honest, i don’t really know that checkpoints are actually helping us, given that our source of truth about what’s been done is our transaction log
they’ve certainly made things a lot more difficult to work with, given that two successive test runs have differing behaviour
You will still want them because you need a way for the peer to pick back up if it crashes
If you're just running tests then use a new checkpoint key each time or force reset the key
totally get that. what’s frustrating is when i do resume a checkpoint, the job doesn’t stop when i try to reset the system
i’m narrowing in on why, i think.
Sounds like a bug?
i think i need to learn about how to surgically clear zookeeper data. it’s a black box to me right now
ok. so when i ensure a fresh onyx/id and checkpoint, it gets to ‘waiting for peers / enough peers are ready’. if not, it never reaches that state. so something about what we’re doing is borking the ZK state in some way
oh, my, gosh. i’m an idiot.
Heh, what happened?
our test server setup redeploys the app from the build server when you restart the service
including the config file
so i’d edit config, it’d restart, wiping my edits
Oops. That explains that
i’ve made checkpoint resetting configurable now. testing...
ITS WORKINGGGGGG
right. now i can finally get back to testing multiple servers together
awesome
:onyx/max-pending doc on cheatsheet has a typo: "- exhibiting backpressure to upstream message produces.”, should be producers
sure thing
nothing motivates tidying up the place like expecting respected visitors
refactoring stuff as i write those docs
I would still like to go back and make the cheat sheet fancier. Searching was a great idea.
one easy way is just a SHOW ALL flag
then you can use page search
Hm, true!
It wouldn’t be that hard to add search anyway
i know - i had fun doing exactly that with the codex
http://www.stuttaford.me/codex https://github.com/robert-stuttaford/stuttaford.me/blob/master/src/stuttaford/codex.cljs
Ah, handy! Thank you @robert-stuttaford
view-source:http://www.stuttaford.me/codex/ has the dataset
really need to update this list. so much more good stuff since i last did
like Onyx heh
Hah. Yeah thats exactly the functionality I'd like to see.
@robert-stuttaford: I'm gonna be doing a talk at Clojure/west called Inside Onyx. It's a deep dive of how everything actually works. I can give you and your team a preview if you want to demo it.
man that’d be awesome! via hangout?
Sure. Maybe late March. I need to sit down and write it, I dont think it'll take too long though.
that’d be seriously awesome
I did a full codebase walkthrough with some people last week. 2.5 hours covered .. I'd say half the core codebase. Its wild remembering how much has gone into making core featureful and stable.
Gonna break for lunch, back later