datomic 2019-10-21 | Slack Archive

Brian14:10:40

I'm using Datomic Cloud and therefore lots of AWS stuff. Does anyone know of where I can ask questions regarding AWS stuff?

ghadi14:10:47

ask away @brian.rogers , it’s a big room

ghadi14:10:48

there’s also an #aws channel

❤️ 4

Brian14:10:29

I'll ask there. Thanks!

jaret15:10:21

#datomic Cloud 535-8811 now available. https://forum.datomic.com/t/datomic-cloud-535-8812/1214

jaret15:10:24

#datomic 0.9.5981 now available. https://forum.datomic.com/t/datomic-0-9-5981-now-available/1213

favila15:10:41

docs for index-parallelism say: >If you have high write volumes, a transactor with plenty of CPUs to spare, and are using a scalable , you can set index-parallelism as high as 8 to speed up indexing jobs:

favila15:10:55

What is the missing word/phrase after “scalable”?

Joe Lane15:10:08

I'm going to guess "backend" but, again, it's a guess.

jaret15:10:29

Should say storage with a link to the storage docs. I am fixing it. Org mode error 🙂

jaret15:10:32

thanks for catching that

souenzzo18:10:44

Any news/hope about datomic-free?

Joe Lane15:10:29

@jaret is index-parallelism pre-enabled on datomic cloud with this release? Is it something cloud users should be thinking of?

jaret15:10:46

This feature is already pre-enabled in cloud.

stuarthalloway15:10:59

and always has been

Joe Lane15:10:52

Ha thanks for answering my current and then immediate next question. See you guys at the Conj!

Brian17:10:18

We have a Datomic db running in our closet that we want to host in AWS. We already have a stack set up and some db's already running in AWS. We have extracted the database from our closet server and are now looking to restore it in AWS. Can someone point me in the right direction for how we can do that? https://docs.datomic.com/on-prem/backup.html looks promising but that is for on-prem and I'm not sure that's what I need

favila17:10:12

are you moving from on-prem to cloud datomic? Not merely on-prem in closet to on-prem on aws. There’s no supported migration from on-prem to cloud systems https://docs.datomic.com/on-prem/moving-to-cloud.html

Brian17:10:01

Does "no supported migration" means there is no easy-button or does it mean that it is not possible?

ghadi17:10:39

you can easily move your on-prem to AWS running on-prem

ghadi17:10:31

by... running on-prem in your AWS EC2 instance

ghadi17:10:45

(on-prem to Datomic Cloud is a different thing as @U09R86PA4 mentions)

favila17:10:14

it’s possible if you do it yourself

favila17:10:45

i.e. some variation of read each tx from the old db, make a new tx for it, transact it into the new cloud db

favila17:10:26

there are feature and other differences between on-prem and cloud that you will have to account for

favila17:10:36

but there’s no easy backup-and-restore

Msr Tim23:10:12

Hi I am setting up a new datomic system in a VPC that needs to be accessed by kubernetes container running in another vpc

Msr Tim23:10:25

i followed the instructions here https://docs.datomic.com/cloud/operation/client-applications.html#vpc-peering

Msr Tim23:10:59

2019-10-21 23:02:05,824 [main] ERROR app.core - {:what :uncaught-exception, :exception #error {
 :cause :server-type must be :cloud, :peer-server, or :local
 :data {:cognitect.anomalies/category :cognitect.anomalies/incorrect, :cognitect.anomalies/message :server-type must be :cloud, :peer-server, or :local}
 :via
 [{:type java.lang.RuntimeException
   :message could not start [#'spot-app.db.core/conn] due to
   :at [mount.core$up$fn__385 invoke core.cljc 80]}
  {:type clojure.lang.ExceptionInfo
   :message :server-type must be :cloud, :peer-server, or :local
   :data {:cognitect.anomalies/category :cognitect.anomalies/incorrect, :cognitect.anomalies/message :server-type must be :cloud, :peer-server, or :local}
   :at [datomic.client.api.impl$incorrect invokeStatic impl.clj 42]}]
 :trace
 [[datomic.client.api.impl$incorrect invokeStatic impl.clj 42]
  [datomic.client.api.impl$incorrect invoke impl.clj 40]

Msr Tim23:10:37

its failing at this line (def conn (d/connect client {:db-name "movies"}))

favila12:10:59

The cause of your error is something in client: a missing or bad :server-type.

favila12:10:24

how do you construct your client? that is where the problem lies

Msr Tim12:10:08

https://docs.datomic.com/cloud/getting-started/connecting.html

Msr Tim12:10:22

like its described there

Msr Tim12:10:50

(require '[datomic.client.api :as d])

(def cfg {:server-type :ion
          :region "<your AWS Region>" ;; e.g. us-east-1
          :system "<system-name>"
          :creds-profile "<your_aws_profile_if_not_using_the_default>"
          :endpoint ".<system-name>.<region>."
          :proxy-port 8182})

(def client (d/client cfg))

Msr Tim12:10:10

it works perfectly locally on my machine via the bastion

Msr Tim12:10:24

but gives me that error on k8s

Msr Tim12:10:32

so it cant be the configuration

favila12:10:36

k8s is not an ion

Msr Tim12:10:49

oooh

favila12:10:55

you are connecting from “outside” the ion cluster