Fork me on GitHub
Pieter Slabbert07:01:26

I have a transaction id and I want to be able to see everything done in that transaction, but so far I can't find a way to do that. Something like

(d/q '[:find ?e ?attr ?val
       :in $ ?tx
       [?e ?attr ?val ?tx true]]
     db tx-id)
Gives me :db.error/insufficient-binding Insufficient binding of db clause: [?e ?attr ?val ?tx true] would cause full scan Is there a way to do this?


Maybe you could use tx-range with log ?

Pieter Slabbert09:01:43

@U07FCNURX Thanks! That gave me exactly what I needed!

👍 2
Jem McElwain18:01:02

does anyone have any advice about valcache on eks/k8s? i was originally planning on running our peers as statefulsets to simplify the storage topology, but we’ve recently hit a point where statefulset rollout would be too slow… wondering about strategies for warming dynamically provisioned EBS volumes. was considering running some kind of sync from a RWX EFS mount, but worried about increasing complexity of our solution


use dynamo + valcache


not sure you need anything on EBS

Jem McElwain00:01:10

sorry, i’m not sure i understand what you’re suggesting. the peers to need to provision storage dynamically, which in the scope of EKS would be EBS volumes


I don’t think you need EBS on peers @U02AEH4M8GY

Jem McElwain01:01:22

the alternative to EBS is using direct attached storage on the eks ec2 nodes, but this is a huge anti-pattern in k8s land


I want to know why you think you need ebs

Jem McElwain01:01:08

because the data for valcache needs to live on an ssd

Jem McElwain01:01:12

per the documentation


ok you're using valcache, thanks.


and now I see that you wrote that in the first sentence. facepalm forgive me, I have a new infant @U02AEH4M8GY

❤️ 1

thanks! would it be possible to provision an ephemeral PV with a good storage class?


it doesn't need to persist / migrate with pods / be stateful

Jem McElwain02:01:25

yes, totally, i have provisioning dynamic/ephemeral volumes all sorted, but given our shift to k8s is coupled with our desire to increase deployment cadence, i’m worried about cache locality suffering a lot if we’re deploying frequently

Jem McElwain02:01:43

since the volumes will be totally cold each time a peer starts


you should open up a question with the datomic team (see topic). they'll have helpful answers (I don't work for them)


totally get your situation now (finally 🙂 )