Fork me on GitHub
#datomic
<
2018-03-14
>
Hendrik Poernama07:03:02

is there a documentation on datomic reader macros? #db/fn, #datom, etc

rauh07:03:46

@poernahi It's documented in d/function

gworley317:03:33

i'm thinking about migrating datastores used to power a datomic install. has anyone else done something like this or is there documentation on how to do it with zero downtime?

gworley317:03:23

i see there is a way to backup and restore, which gets most of the way there, but that would require taking the system down during the process since otherwise i'm not sure how i'd get the latest changes that happen between when the backup starts and the restore completes

gworley318:03:17

and ideally i'd like to be able to run both backends side-by-side for a while so i could very performance of the new datastore in production without being fully committed to it

stijn19:03:20

is there an option to launch datomic cloud from terraform?

marshall19:03:19

@amarjeet is your system running with the correct AWS credentials (i.e. in a role or with ambient creds)? Is it running on an EC2 instance? If so, is it in the Datomic VPC? What security group?

amarjeet19:03:16

yes, those things seem fine. My datomic-socks-proxy consol prints this debug1: channel 2: free: direct-tcpip: listening port 8182 for entry.<system-name>.<region>. port 8182, connect from ::1 port xxxxx to ::1 port 8182, nchannels 3

amarjeet19:03:05

and this command curl -x .$DATOMIC_SYSTEM.$ also prints {:s3-auth-path <bucket-name>}

marshall19:03:06

you’re running with a socks proxy or you’re running on AWS?

marshall19:03:30

your client application that is

amarjeet19:03:58

So, while launching datomic cloud, I used socks proxy process

amarjeet19:03:14

Now, I have a pedestal app, that I want to connect with that cloud db

marshall19:03:26

right. and where is your pedestal app running?

amarjeet19:03:33

its my local system

marshall19:03:42

ok. your cfg map doesn’t specify the proxy-port

marshall19:03:21

when you’re running locally through the socks proxy you need to include the :proxy-port in your cfg map

amarjeet19:03:21

okay, so when I specify the port as 8182, I get connect refused error

amarjeet19:03:00

m checking again

marshall19:03:13

your pedestal app (however you’re launching it) will also need to be running with ambient AWS credentials

amarjeet19:03:16

Unable to connect to system: #:cognitect.anomalies{:category :cognitect.anomalies/unavailable, :message "Total timeout 60000 ms elapsed"} thsi is the erro I am getting with proxy-port

amarjeet19:03:58

aws creds mean, I should put the credentials in project.clj as {:user {:aws ...}}

Alex Miller (Clojure team)19:03:34

much better to put them in the ambient environment via standard AWS env vars

marshall19:03:39

i don’t know about lein specifically; i usually use the ambient env creds

Alex Miller (Clojure team)19:03:56

don’t check your aws creds into your git :)

amarjeet19:03:48

okay 🙂 let me try this. I am pretty much newbie to the deployment side of things

amarjeet19:03:50

aah, its connected now

amarjeet19:03:58

thanks much both of you 🙂

Datomic Platonic22:03:33

does the datomic-pro peer server allows backups? we run datomic.peer-server on localhost: Serving datomic:<mem://hello> and then try a backup but keep getting Invalid database URI errors

marshall22:03:15

you can’t run a backup of a mem database

marshall22:03:37

backup and restore require storage

Datomic Platonic22:03:07

got it -- thanks... we ultimately plan to run on AWS but want to understand backup/restore before we push there

marshall22:03:48

you can run a local transactor with a dev database and use both peer-server against it as well as backup and restore

Datomic Platonic22:03:42

thanks @marshall, we'll keep reading...

Christian Johansen22:03:17

When using Dynamo as the storage backend, is it safe to rely on Dynamo snapshots for backup, or should we still be using Datomic’s backup tool?

marshall23:03:42

You should use datomic backup

marshall23:03:30

Ddb snapshots don't provide the required semantics for a consistent copy of a datomic db