This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-18
Channels
- # beginners (25)
- # boot (30)
- # cljs-dev (22)
- # cljsjs (2)
- # cljsrn (1)
- # clojars (4)
- # clojure (223)
- # clojure-boston (1)
- # clojure-dusseldorf (1)
- # clojure-gamedev (8)
- # clojure-italy (5)
- # clojure-russia (122)
- # clojure-sg (3)
- # clojure-spec (26)
- # clojure-uk (42)
- # clojurescript (69)
- # clojuresque (10)
- # core-async (25)
- # cursive (10)
- # datascript (5)
- # datomic (12)
- # emacs (18)
- # garden (1)
- # interop (1)
- # jobs (1)
- # jobs-discuss (10)
- # leiningen (2)
- # liberator (1)
- # lumo (21)
- # nyc (2)
- # off-topic (210)
- # om (11)
- # om-next (3)
- # onyx (1)
- # pedestal (6)
- # re-frame (10)
- # rum (9)
- # specter (38)
- # uncomplicate (1)
- # vim (23)
- # yada (22)
Released Datofu, a library of common Datomic utilities https://github.com/vvvvalvalval/datofu
@val_waeselynck The idempotency of the db functions, is that implemented on top of your migration system? (conformity style basically)
@dominicm no, it's just that installing the schema for a transaction fn is idempotent
I’m getting a failed heartbeat on a datomic:dev://
database. Incidentally, it keeps happening after running a large import, though I’m not suggesting that’s related. Any ideas?
@val_waeselynck the ordering, do you know how well that performs out of interest?
@dominicm never tested it in production with more than a few dozen items, in which case it showed no performance issue
but that question is a bit difficult to answer - it depends on the data distribution and the queries you run on it
@val_waeselynck I agree, thought as much 😛
@uwo heartbeat fails when the transactor can no longer write to storage. I know this is just DEV but have you configured HA ? http://docs.datomic.com/ha.html
its kind of hacky, but you might also be able to up the heartbeat-interval-msec in your transactor properties file to give you some more breathing room before failover