Fork me on GitHub
#datomic
<
2017-04-18
>
val_waeselynck16:04:06

Released Datofu, a library of common Datomic utilities https://github.com/vvvvalvalval/datofu

dominicm16:04:47

@val_waeselynck The idempotency of the db functions, is that implemented on top of your migration system? (conformity style basically)

val_waeselynck16:04:20

@dominicm no, it's just that installing the schema for a transaction fn is idempotent

uwo16:04:23

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?

dominicm16:04:23

@val_waeselynck the ordering, do you know how well that performs out of interest?

val_waeselynck16:04:31

@dominicm never tested it in production with more than a few dozen items, in which case it showed no performance issue

val_waeselynck16:04:00

but that question is a bit difficult to answer - it depends on the data distribution and the queries you run on it

dominicm16:04:25

@val_waeselynck I agree, thought as much 😛

jaret18:04:50

@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

jaret18:04:33

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

jaret18:04:05

but if its failing routinely that likely won't matter and you need to figure out what might be causing storage to be unreachable

uwo19:04:24

@jaret thanks, that’s very useful info! I suspect our culprit was a deployed artifact with a mismatched peer version number, though I can’t be sure. But I haven’t run into the issue since ensuring that we were using the right version of the peer library. lame explanation, sorry!