This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-28
Channels
- # aleph (1)
- # arachne (4)
- # beginners (13)
- # boot (18)
- # clara (7)
- # cljs-dev (156)
- # cljsrn (278)
- # clojure (163)
- # clojure-conj (5)
- # clojure-dev (1)
- # clojure-losangeles (1)
- # clojure-poland (2)
- # clojure-sg (1)
- # clojure-spec (15)
- # clojure-uk (17)
- # clojurescript (275)
- # data-science (5)
- # datomic (23)
- # emacs (10)
- # leiningen (1)
- # lumo (16)
- # off-topic (98)
- # onyx (10)
- # parinfer (83)
- # re-frame (18)
- # reagent (47)
- # remote-jobs (1)
- # ring (1)
- # ring-swagger (5)
- # rum (6)
- # specter (8)
- # vim (5)
@robert-stuttaford how do you deal with needing to up the write capacity on dynamo before doing the restore? did you automate that?
@erichmond yes, we have a totally scripted process that ups DDB, restores, downs DDB, cycles the transactor, and restarts all the connected peer service apps on their instances
does the time it takes to connect a peer increase as the size of the db increases? In dev, I’m noticing that some datomic instances are taking longer to connect to than others. (They’re all setup the same way with sql storage).
@uwo peers need to grab all the idents and the live index. so if your live index is large (ie just before indexing job) it’ll take longer to start up
we saw a substantial peer startup time when we doubled our transactor instance size 🙂
@erichmond i live in Cape Town, South Africa, so dinner might be a little tough to swing 😁
@robert-stuttaford thanks!
No problem! Just checked google maps. It appears the midway point between NYC and Cape Town is roughly the Cape Verdean Islands. We just each take a quick flight over there.
we’ll be the best two Clojure developers for miles!
that won’t be awkward at all
@robert-stuttaford do you schedule your own indexing jobs outside of imports?
@uwo not so far